macintosh: fix possible memory leak in macio_add_one_device()
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.16% (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 19ded60b40e86b0903c8d5bd0161437ed5107a8b, 2ac0a7059b7bcbed35bfffa34a82c9a9e99638ef, 35858b87a943917fa30172aa4bf01ce7adbcb42c.
Low priority for now. Upgrade to Linux Linux 19ded60b40e86b0903c8d5bd0161437ed5107a8b, 2ac0a7059b7bcbed35bfffa34a82c9a9e99638ef, 35858b87a943917fa30172aa4bf01ce7adbcb42c 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: macintosh: fix possible memory leak in macio_add_one_device() Afer commit 1fa5ae857bb1 ("driver core: get rid of struct device's bus_id string array"), the name of device is allocated dynamically. It needs to be freed when of_device_register() fails. Call put_device() to give up the reference that's taken in device_initialize(), so that it can be freed in kobject_cleanup() when the refcount hits 0. macio device is freed in macio_release_dev(), so the kfree() can be removed.
- Published
- Oct 4, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-401
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.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.
| 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 kernel2.6.30 and later · before 4.9.337
- linux linux kernel4.10 and later · before 4.14.303
- linux linux kernel4.15 and later · before 4.19.270
- linux linux kernel4.20 and later · before 5.4.229
- linux linux kernel5.5 and later · before 5.10.163
- linux linux kernel5.11 and later · before 5.15.86
- linux linux kernel5.16 and later · before 6.0.16
- linux linux kernel6.1 and later · before 6.1.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
- 2.6.30affected
- 1fa5ae857bb14f6046205171d98506d8112dd74e and later · before 3a866ff6fc2232c8e393cdb55ffb8ce947349e03affected · git
- 1fa5ae857bb14f6046205171d98506d8112dd74e and later · before aa9054267366ff0a382d403d17728e21951ddbb9affected · git
- 1fa5ae857bb14f6046205171d98506d8112dd74e and later · before 35858b87a943917fa30172aa4bf01ce7adbcb42caffected · git
- 1fa5ae857bb14f6046205171d98506d8112dd74e and later · before b29a2f1dd33ae9b94821ab2f4d398b9081786748affected · git
- 1fa5ae857bb14f6046205171d98506d8112dd74e and later · before 2ac0a7059b7bcbed35bfffa34a82c9a9e99638efaffected · git
- 1fa5ae857bb14f6046205171d98506d8112dd74e and later · before 19ded60b40e86b0903c8d5bd0161437ed5107a8baffected · git
- 1fa5ae857bb14f6046205171d98506d8112dd74e and later · before ca765257feb89dacf604ced9cd233db5f865dee0affected · git
- 1fa5ae857bb14f6046205171d98506d8112dd74e and later · before 76837e7f6b30da72ad59f56291e22804a219e015affected · git
- 1fa5ae857bb14f6046205171d98506d8112dd74e and later · before 5ca86eae55a2f006e6c1edd2029b2cacb6979515affected · git
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.4-1 | 6.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- 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
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2022-50471Oct 4, 2025 · xen/gntdev: Accommodate VMA splitting22Monitor
- ← EarlierCVE-2022-50473Oct 4, 2025 · cpufreq: Init completion before kobject_init_and_add()22Monitor
- Later →CVE-2022-50475Oct 4, 2025 · RDMA/core: Make sure "ib_port" is valid when access sysfs node22Monitor
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 | 19ded60b40e86b0903c8d5bd0161437ed5107a8b | Vendor (CNA) |
| Linux Linux | 2ac0a7059b7bcbed35bfffa34a82c9a9e99638ef | Vendor (CNA) |
| Linux Linux | 35858b87a943917fa30172aa4bf01ce7adbcb42c | Vendor (CNA) |
| Linux Linux | 3a866ff6fc2232c8e393cdb55ffb8ce947349e03 | Vendor (CNA) |
| Linux Linux | 5ca86eae55a2f006e6c1edd2029b2cacb6979515 | Vendor (CNA) |
| Linux Linux | 76837e7f6b30da72ad59f56291e22804a219e015 | Vendor (CNA) |
| Linux Linux | aa9054267366ff0a382d403d17728e21951ddbb9 | Vendor (CNA) |
| Linux Linux | b29a2f1dd33ae9b94821ab2f4d398b9081786748 | Vendor (CNA) |
| Linux Linux | ca765257feb89dacf604ced9cd233db5f865dee0 | Vendor (CNA) |
| debian:linux | 6.1.4-1 · 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
- 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-401 · Missing Release of Memory after Effective LifetimeCVSS 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/2ac0a7059b7bcbed35bfffa34a82c9a9e99638ef
- git.kernel.org/stable/c/35858b87a943917fa30172aa4bf01ce7adbcb42c
- git.kernel.org/stable/c/3a866ff6fc2232c8e393cdb55ffb8ce947349e03
- git.kernel.org/stable/c/5ca86eae55a2f006e6c1edd2029b2cacb6979515
- git.kernel.org/stable/c/76837e7f6b30da72ad59f56291e22804a219e015
- git.kernel.org/stable/c/aa9054267366ff0a382d403d17728e21951ddbb9
- git.kernel.org/stable/c/b29a2f1dd33ae9b94821ab2f4d398b9081786748
- git.kernel.org/stable/c/ca765257feb89dacf604ced9cd233db5f865dee0
Vendor advisories and official records. Exploit/PoC links are deliberately left out.