CVE-2024-53209: bnxt_en: Fix receive ring space parameters when XDP is active
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.62% (FIRST EPSS); higher than 50.1% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 3051a77a09dfe3022aa012071346937fdf059033, 6.1.140, 6.5; azl3 kernel 6.6.85.1-1 on Azure Linux 3.0 6.6.85.1-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.85.1-1.
- Severity is disputed: the assigning authority (CNA) scores it 9.8, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 3051a77a09dfe3022aa012071346937fdf059033, 6.1.140, 6.5; azl3 kernel 6.6.85.1-1 on Azure Linux 3.0 6.6.85.1-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.85.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Fix receive ring space parameters when XDP is active The MTU setting at the time an XDP multi-buffer is attached determines whether the aggregation ring will be used and the rx_skb_func handler. This is done in bnxt_set_rx_skb_mode(). If the MTU is later changed, the aggregation ring setting may need to be changed and it may become out-of-sync with the settings initially done in bnxt_set_rx_skb_mode(). This may result in random memory corruption and crashes as the HW may DMA data larger than the allocated buffer size, such as: BUG: kernel NULL pointer dereference, address: 00000000000003c0 PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 17 PID: 0 Comm: swapper/17 Kdump: loaded Tainted: G S OE 6.1.0-226bf9805506 #1 Hardware name: Wiwynn Delta Lake PVT BZA.02601.0150/Delta Lake-Class1, BIOS F0E_3A12 08/26/2021 RIP: 0010:bnxt_rx_pkt+0xe97/0x1ae0 [bnxt_en] Code: 8b 95 70 ff ff ff 4c 8b 9d 48 ff ff ff 66 41 89 87 b4 00 00 00 e9 0b f7 ff ff 0f b7 43 0a 49 8b 95 a8 04 00 00 25 ff 0f 00 00 <0f> b7 14 42 48 c1 e2 06 49 03 95 a0 04 00 00 0f b6 42 33f RSP: 0018:ffffa19f40cc0d18 EFLAGS: 00010202 RAX: 00000000000001e0 RBX: ffff8e2c805c6100 RCX: 00000000000007ff RDX: 0000000000000000 RSI: ffff8e2c271ab990 RDI: ffff8e2c84f12380 RBP: ffffa19f40cc0e48 R08: 000000000001000d R09: 974ea2fcddfa4cbf R10: 0000000000000000 R11: ffffa19f40cc0ff8 R12: ffff8e2c94b58980 R13: ffff8e2c952d6600 R14: 0000000000000016 R15: ffff8e2c271ab990 FS: 0000000000000000(0000) GS:ffff8e3b3f840000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000000003c0 CR3: 0000000e8580a004 CR4: 00000000007706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: <IRQ> __bnxt_poll_work+0x1c2/0x3e0 [bnxt_en] To address the issue, we now call bnxt_set_rx_skb_mode() within bnxt_change_mtu() to properly set the AGG rings configuration and update rx_skb_func based on the new MTU value. Additionally, BNXT_FLAG_NO_AGG_RINGS is cleared at the beginning of bnxt_set_rx_skb_mode() to make sure it gets set or cleared based on the current MTU.
- Published
- Dec 27, 2024
- Updated
- Oct 15, 2026
- EPSS
- 0.6% · 50th percentile
- CWE
- CWE-476
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 9.8
- 4.3 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.1.45 and later · before 6.2
- linux linux kernel6.4.10 and later · before 6.11.11
- linux linux kernel6.12 and later · before 6.12.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 893096a7e5fd61cb666b4ead2fa69324e1f2aade, 6.5affected
- 421e02bda0570eeb11636544fe97ec3097d1bb92 and later · before b7fd784d7c6a1bd927a23e0d06f09a776ee3889baffected · git
- 08450ea98ae98d5a35145b675b76db616046ea11 and later · before 7f306c651feab2f3689185f60b94e72b573255dbaffected · git
- 08450ea98ae98d5a35145b675b76db616046ea11 and later · before bf54a7660fc8d2166f41ff1d67a643b15d8b2250affected · git
- 08450ea98ae98d5a35145b675b76db616046ea11 and later · before 84353386762a0a16dd444ead76c012e167d89b41affected · git
- 08450ea98ae98d5a35145b675b76db616046ea11 and later · before 3051a77a09dfe3022aa012071346937fdf059033affected · git
- 6.1.45 and later · before 6.1.140affected · semver
- 6.4.10 and later · before 6.5affected · semver
- before 6.5not affected · semver
- 6.1.140 and later · up to and including 6.1.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | linux-6.1 | before 6.1.140-1~deb11u1 | 6.1.140-1~deb11u1 |
| Debian:12 | linux | before 6.1.140-1 | 6.1.140-1 |
| Debian:13 | linux | before 6.12.3-1 | 6.12.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-53195Dec 27, 2024 · KVM: arm64: Get rid of userspace_irqchip_in_use22Monitor
- ← EarlierCVE-2024-53201Dec 27, 2024 · drm/amd/display: Fix null check for pipe_ctx->plane_state in dcn20_program_pipe22Monitor
- Later →CVE-2024-53216Dec 27, 2024 · nfsd: release svc_expkey/svc_export with rcu_work31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3051a77a09dfe3022aa012071346937fdf059033 | Vendor (CNA) |
| Linux Linux | 6.1.140 | Vendor (CNA) |
| Linux Linux | 6.5 | Vendor (CNA) |
| Linux Linux | 7f306c651feab2f3689185f60b94e72b573255db | Vendor (CNA) |
| Linux Linux | 84353386762a0a16dd444ead76c012e167d89b41 | Vendor (CNA) |
| Linux Linux | b7fd784d7c6a1bd927a23e0d06f09a776ee3889b | Vendor (CNA) |
| Linux Linux | bf54a7660fc8d2166f41ff1d67a643b15d8b2250 | Vendor (CNA) |
| azl3 kernel 6.6.85.1-1 on Azure Linux 3.0 | 6.6.85.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 | 6.6.85.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.140-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.1 | 6.1.140-1~deb11u1 · Debian:11 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/7f306c651feab2f3689185f60b94e72b573255db
- git.kernel.org/stable/c/84353386762a0a16dd444ead76c012e167d89b41
- git.kernel.org/stable/c/b7fd784d7c6a1bd927a23e0d06f09a776ee3889b
- git.kernel.org/stable/c/bf54a7660fc8d2166f41ff1d67a643b15d8b2250
- lists.debian.org/debian-lts-announce/2025/08/msg00010.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.