dpaa2-eth: put MAC endpoint device on disconnect
In the Linux kernel, the following vulnerability has been resolved: dpaa2-eth: put MAC endpoint device on disconnect fsl_mc_get_endpoint() returns the MAC endpoint device with a reference taken through device_find_child(). The Ethernet connect path stores that device in mac->mc_dev and keeps it for the lifetime of the connected MAC object. However, the disconnect path only disconnects and closes the MAC before freeing the dpaa2_mac object. It does not drop the endpoint device reference stored in mac->mc_dev, so every successful connect leaks that device reference when the MAC is later disconnected. Drop the endpoint device reference after closing the MAC and before freeing the dpaa2_mac object.
- Published
- Aug 10, 2026
- Updated
- Aug 19, 2026
- EPSS
- 0.2% · 11th 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
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.5affected
- 71947923089353f23f4f210864903c4dcf2c1696 and later · before 6b6ffdb9ca4547a3c4c274aa3e25b6c68dbc62e1affected · git
- 71947923089353f23f4f210864903c4dcf2c1696 and later · before 1974127776da46a000c61f36d4946799ea6d4f51affected · git
- 71947923089353f23f4f210864903c4dcf2c1696 and later · before 915012e923316b8b5d5bf8fc771617b47bd7572daffected · git
- 71947923089353f23f4f210864903c4dcf2c1696 and later · before e23e4a3b9dfd893469c731318d409cdf04fb1ddfaffected · git
- 71947923089353f23f4f210864903c4dcf2c1696 and later · before f112df0744e2d77baa68eeebb860021bbaaa022aaffected · git
- 71947923089353f23f4f210864903c4dcf2c1696 and later · before a3cecf169cc652b558d08661bb6ce55e4c933ec0affected · git
- 71947923089353f23f4f210864903c4dcf2c1696 and later · before b4b201cc93ff70150853aba03e14d314d1980ca0affected · git
- before 5.5not affected · semver
- 5.15.216 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.6-1 | 7.1.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
- 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 | 1974127776da46a000c61f36d4946799ea6d4f51 | Vendor (CNA) |
| Linux Linux | 6b6ffdb9ca4547a3c4c274aa3e25b6c68dbc62e1 | Vendor (CNA) |
| Linux Linux | 915012e923316b8b5d5bf8fc771617b47bd7572d | Vendor (CNA) |
| Linux Linux | a3cecf169cc652b558d08661bb6ce55e4c933ec0 | Vendor (CNA) |
| Linux Linux | b4b201cc93ff70150853aba03e14d314d1980ca0 | Vendor (CNA) |
| Linux Linux | e23e4a3b9dfd893469c731318d409cdf04fb1ddf | Vendor (CNA) |
| Linux Linux | f112df0744e2d77baa68eeebb860021bbaaa022a | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| 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
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.
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/1974127776da46a000c61f36d4946799ea6d4f51
- git.kernel.org/stable/c/6b6ffdb9ca4547a3c4c274aa3e25b6c68dbc62e1
- git.kernel.org/stable/c/915012e923316b8b5d5bf8fc771617b47bd7572d
- git.kernel.org/stable/c/a3cecf169cc652b558d08661bb6ce55e4c933ec0
- git.kernel.org/stable/c/b4b201cc93ff70150853aba03e14d314d1980ca0
- git.kernel.org/stable/c/e23e4a3b9dfd893469c731318d409cdf04fb1ddf
- git.kernel.org/stable/c/f112df0744e2d77baa68eeebb860021bbaaa022a
Vendor advisories and official records. Exploit/PoC links are deliberately left out.