Kernel crash via stale receive-buffer configuration
Published Dec 27, 2024 · Updated Aug 5, 2026
Memory corruption in the Linux bnxt_en driver allows local users to crash the kernel after XDP attachment and an MTU change. bnxt_change_mtu() fails to rerun bnxt_set_rx_skb_mode(), leaving aggregation-ring and receive-handler settings stale so hardware can DMA packets larger than the allocated buffer. Triggering the fault requires a bnxt_en network device, XDP multi-buffer attachment, and a later MTU change; the documented consequence is memory corruption and a kernel crash.
Summary
What happened
Memory corruption in the Linux bnxt_en driver allows local users to crash the kernel after XDP attachment and an MTU change. bnxt_change_mtu() fails to rerun bnxt_set_rx_skb_mode(), leaving aggregation-ring and receive-handler settings stale so hardware can DMA packets larger than the allocated buffer. Triggering the fault requires a bnxt_en network device, XDP multi-buffer attachment, and a later MTU change; the documented consequence is memory corruption and a kernel crash.
The record
- CVE
- CVE-2024-53209
- Published
- Dec 27, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 27, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=08450ea98ae98d5a35145b675b76db616046ea11 <3051a77a09dfe3022aa012071346937fdf059033
- Affected versionversion=08450ea98ae98d5a35145b675b76db616046ea11 <7f306c651feab2f3689185f60b94e72b573255db
- Affected versionversion=08450ea98ae98d5a35145b675b76db616046ea11 <84353386762a0a16dd444ead76c012e167d89b41
- Affected versionversion=08450ea98ae98d5a35145b675b76db616046ea11 <bf54a7660fc8d2166f41ff1d67a643b15d8b2250
- Affected versionversion=421e02bda0570eeb11636544fe97ec3097d1bb92 <b7fd784d7c6a1bd927a23e0d06f09a776ee3889b
- Affected versionversion=6.1.45 <6.1.140
- Affected versionversion=6.4.10 <6.5
- Affected versionversion=6.5
- Affected versionversion=893096a7e5fd61cb666b4ead2fa69324e1f2aade
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo