CVE-2026-97440: net: qrtr: fix node refcount leak on ctrl packet alloc failure
Noroxi assessment
Priority: Monitor (action score 0/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.17% (FIRST EPSS).
- Fixed version: Linux Linux 3b09ff54114566864eea59020f6b69c5bb325b9d, 477353db343663d5502ca442c6de785d2f23f273, 78d066ecac9ce50441d4affae0df2093c4c3e62e; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
Low priority for now. Upgrade to Linux Linux 3b09ff54114566864eea59020f6b69c5bb325b9d, 477353db343663d5502ca442c6de785d2f23f273, 78d066ecac9ce50441d4affae0df2093c4c3e62e; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.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: net: qrtr: fix node refcount leak on ctrl packet alloc failure qrtr_send_resume_tx() calls qrtr_node_lookup() which takes a reference on the returned node. If the subsequent call to qrtr_alloc_ctrl_packet() fails due to memory allocation failure, the function returns -ENOMEM without calling qrtr_node_release() to release the node reference. Add qrtr_node_release(node) before returning on the allocation failure path to properly release the reference.
- Published
- Sep 24, 2026
- Updated
- Oct 3, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- 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.
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.
—
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
- 5.6affected
- cb6530b99fafea6c0636c4640bd21301d12cdbc9 and later · before 78d066ecac9ce50441d4affae0df2093c4c3e62eaffected · git
- cb6530b99fafea6c0636c4640bd21301d12cdbc9 and later · before f3e90fbcd2d5ec1632bc2e8cdd1218f56bcb5fcfaffected · git
- cb6530b99fafea6c0636c4640bd21301d12cdbc9 and later · before c3515740174b778d0ee44acc477b51a6478da6b8affected · git
- cb6530b99fafea6c0636c4640bd21301d12cdbc9 and later · before f76a39c45182d9137e053081cee9f2c197404ce6affected · git
- cb6530b99fafea6c0636c4640bd21301d12cdbc9 and later · before 477353db343663d5502ca442c6de785d2f23f273affected · git
- cb6530b99fafea6c0636c4640bd21301d12cdbc9 and later · before 9d969c98732a4d42212ec580dd5bbad53f246103affected · git
- cb6530b99fafea6c0636c4640bd21301d12cdbc9 and later · before 3b09ff54114566864eea59020f6b69c5bb325b9daffected · git
- before 5.6not affected · semver
- 5.10.271 and later · up to and including 5.10.*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:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-97438Sep 24, 2026 · fs/ntfs3: validate index entry key bounds28Monitor
- ← EarlierCVE-2026-97439Sep 24, 2026 · fs/ntfs3: preserve non-DOS attribute bits in system.dos_attrib0Monitor
- Later →CVE-2026-97441Sep 24, 2026 · ata: ahci: fail probe if BAR too small for claimed ports0Monitor
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 | 3b09ff54114566864eea59020f6b69c5bb325b9d | Vendor (CNA) |
| Linux Linux | 477353db343663d5502ca442c6de785d2f23f273 | Vendor (CNA) |
| Linux Linux | 78d066ecac9ce50441d4affae0df2093c4c3e62e | Vendor (CNA) |
| Linux Linux | 9d969c98732a4d42212ec580dd5bbad53f246103 | Vendor (CNA) |
| Linux Linux | c3515740174b778d0ee44acc477b51a6478da6b8 | Vendor (CNA) |
| Linux Linux | f3e90fbcd2d5ec1632bc2e8cdd1218f56bcb5fcf | Vendor (CNA) |
| Linux Linux | f76a39c45182d9137e053081cee9f2c197404ce6 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/477353db343663d5502ca442c6de785d2f23f273
- git.kernel.org/stable/c/78d066ecac9ce50441d4affae0df2093c4c3e62e
- git.kernel.org/stable/c/9d969c98732a4d42212ec580dd5bbad53f246103
- git.kernel.org/stable/c/c3515740174b778d0ee44acc477b51a6478da6b8
- git.kernel.org/stable/c/f3e90fbcd2d5ec1632bc2e8cdd1218f56bcb5fcf
- git.kernel.org/stable/c/f76a39c45182d9137e053081cee9f2c197404ce6
Vendor advisories and official records. Exploit/PoC links are deliberately left out.