CVE-2026-31621: bnge: return after auxiliary_device_uninit() in error path
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.12% (FIRST EPSS).
- 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.
- Fixed version: Linux Linux 38c383ec6d37f4b5597f8e6a1f5c2ab31ea01d3a, 87bc3557c708110d83086bf091328271298a44e3, 8b0c25528cb64f71a73b5c0d49cbbcb68540a4ce; azl3 kernel 6.6.130.1-3 on Azure Linux 3.0 6.6.134.1-2.
Low priority for now. Upgrade to Linux Linux 38c383ec6d37f4b5597f8e6a1f5c2ab31ea01d3a, 87bc3557c708110d83086bf091328271298a44e3, 8b0c25528cb64f71a73b5c0d49cbbcb68540a4ce; azl3 kernel 6.6.130.1-3 on Azure Linux 3.0 6.6.134.1-2 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: bnge: return after auxiliary_device_uninit() in error path When auxiliary_device_add() fails, the error block calls auxiliary_device_uninit() but does not return. The uninit drops the last reference and synchronously runs bnge_aux_dev_release(), which sets bd->auxr_dev = NULL and frees the underlying object. The subsequent bd->auxr_dev->net = bd->netdev then dereferences NULL, which is not a good thing to have happen when trying to clean up from an error. Add the missing return, as the auxiliary bus documentation states is a requirement (seems that LLM tools read documentation better than humans do...)
- Published
- Apr 24, 2026
- Updated
- Nov 11, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-908
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
Is your version affected? Check itNoroxi 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 |
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
- 6.19affected
- 8ac050ec3b1c0dcb5e89cf86fe2ebe0afcc73554 and later · before 38c383ec6d37f4b5597f8e6a1f5c2ab31ea01d3aaffected · git
- 8ac050ec3b1c0dcb5e89cf86fe2ebe0afcc73554 and later · before 87bc3557c708110d83086bf091328271298a44e3affected · git
- 8ac050ec3b1c0dcb5e89cf86fe2ebe0afcc73554 and later · before 8b0c25528cb64f71a73b5c0d49cbbcb68540a4ceaffected · git
- before 6.19not affected · semver
- 6.19.14 and later · up to and including 6.19.*not affected · semver
- 7.0.1 and later · up to and including 7.0.*not affected · semver
- 7.1 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.19 and later · before 6.19.14
- linux linux kernel7.0 and later · before 7.0.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:14 | linux | before 6.19.14-1 | 6.19.14-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-2026-31619Apr 24, 2026 · ALSA: fireworks: bound device-supplied status before string array lookup22Monitor
- ← EarlierCVE-2026-31620Apr 24, 2026 · ALSA: usx2y: us144mkii: fix NULL deref on missing interface 018Monitor
- Later →CVE-2026-31622Apr 24, 2026 · NFC: digital: Bounds check NFC-A cascade depth in SDD response handler35Monitor
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 | 38c383ec6d37f4b5597f8e6a1f5c2ab31ea01d3a | Vendor (CNA) |
| Linux Linux | 87bc3557c708110d83086bf091328271298a44e3 | Vendor (CNA) |
| Linux Linux | 8b0c25528cb64f71a73b5c0d49cbbcb68540a4ce | Vendor (CNA) |
| azl3 kernel 6.6.130.1-3 on Azure Linux 3.0 | 6.6.134.1-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.19.14-1 · Debian:14 | 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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-50302521 days apartHID: core: zero-initialize the report bufferKEV52Plan
- CVE-2026-5298961 days apartnvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers39Monitor
- CVE-2026-6385786 days apartnet: airoha: Do not read uninitialized fragment address in airoha_dev_xmit()39Monitor
- CVE-2026-5322562 days apartsctp: fix uninit-value in __sctp_rcv_asconf_lookup()36Monitor
- CVE-2026-5317062 days apartaccel/ethosu: reject DMA commands with uninitialized length35Monitor
- CVE-2026-4313912 days apartxfrm6: fix uninitialized saddr in xfrm6_get_saddr()34Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
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-908 · Use of Uninitialized ResourceCVSS 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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.