net: mana: Validate the packet length reported by the NIC
In the Linux kernel, the following vulnerability has been resolved: net: mana: Validate the packet length reported by the NIC Validate the packet length reported in the RX CQE before passing it to skb processing. The CQE is supplied by the NIC device and should not be blindly trusted.
- Published
- Aug 15, 2026
- Updated
- Aug 23, 2026
- EPSS
- 0.7% · 53th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 9.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
—
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.13affected
- ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and later · before a631f82f89c76084ad5b2b9c043d3b391ffa56d8affected · git
- ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and later · before d2568e64d01f480200063fadd67d6938f676c66faffected · git
- ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and later · before 2e276b14b6d378372bf0152df89286cbe7632fb0affected · git
- ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and later · before 6080189291d958604dcefe513a13900835ac982faffected · git
- ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and later · before 6d13eaa13341a8f80aaf86f78591e1b1d393711daffected · git
- ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and later · before 282c5214ca4eb3799158c76782646e86d2945d1baffected · git
- ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and later · before 2e2a83b4998af4384e677d3b2ac08565274279bfaffected · git
- before 5.13not affected · semver
- 5.15.217 and later · up to and including 5.15.*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.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-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
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
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 | 282c5214ca4eb3799158c76782646e86d2945d1b | Vendor (CNA) |
| Linux Linux | 2e276b14b6d378372bf0152df89286cbe7632fb0 | Vendor (CNA) |
| Linux Linux | 2e2a83b4998af4384e677d3b2ac08565274279bf | Vendor (CNA) |
| Linux Linux | 6080189291d958604dcefe513a13900835ac982f | Vendor (CNA) |
| Linux Linux | 6d13eaa13341a8f80aaf86f78591e1b1d393711d | Vendor (CNA) |
| Linux Linux | a631f82f89c76084ad5b2b9c043d3b391ffa56d8 | Vendor (CNA) |
| Linux Linux | d2568e64d01f480200063fadd67d6938f676c66f | Vendor (CNA) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-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
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/282c5214ca4eb3799158c76782646e86d2945d1b
- git.kernel.org/stable/c/2e276b14b6d378372bf0152df89286cbe7632fb0
- git.kernel.org/stable/c/2e2a83b4998af4384e677d3b2ac08565274279bf
- git.kernel.org/stable/c/6080189291d958604dcefe513a13900835ac982f
- git.kernel.org/stable/c/6d13eaa13341a8f80aaf86f78591e1b1d393711d
- git.kernel.org/stable/c/a631f82f89c76084ad5b2b9c043d3b391ffa56d8
- git.kernel.org/stable/c/d2568e64d01f480200063fadd67d6938f676c66f
Vendor advisories and official records. Exploit/PoC links are deliberately left out.