CVE-2023-53342
BaseFortify
Publication date: 2025-09-17
Last updated on: 2025-12-11
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 6.1 (inc) to 6.1.46 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.4.11 (exc) |
| linux | linux_kernel | 6.5 |
| linux | linux_kernel | 6.5 |
| linux | linux_kernel | 6.5 |
| linux | linux_kernel | 6.5 |
| linux | linux_kernel | 6.5 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel's Marvell Prestera network driver involves incorrect handling of IPv4 routes that reference a nexthop via its ID (nhid). The issue arises because the code used an incorrect function (fib_info_nh()) instead of the correct one (fib_info_nhc()) to handle these routes, which triggers kernel warnings and potentially unstable behavior when adding such routes.
How can this vulnerability impact me? :
This vulnerability can cause kernel warnings and potentially unstable or incorrect behavior in the network routing subsystem when IPv4 routes referencing nexthops by ID are added. This could lead to network disruptions or degraded performance on affected systems using the Marvell Prestera driver.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing kernel warning messages related to the prestera module when adding IPv4 routes referencing a nexthop via its id. The example commands that trigger the issue are: $ ip link set up swp5 $ ip a a 10.0.0.1/24 dev swp5 $ ip nexthop add dev swp5 id 20 via 10.0.0.2 $ ip route add 10.0.1.0/24 nhid 20 If the vulnerability is present, kernel warnings similar to the following will appear in the system logs: WARNING: CPU: ... at include/net/nexthop.h:468 __prestera_fi_is_direct+0x2c/0x68 [prestera] Monitoring dmesg or system logs for such warnings after running these commands can help detect the vulnerability.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this vulnerability is fixed. The fix replaces calls to fib_info_nh() with fib_info_nhc() in handling IPv4 routes referencing a nexthop via its id in the prestera driver. Until the update is applied, avoid adding IPv4 routes that reference a nexthop via nhid to prevent triggering the vulnerability.