CVE-2026-46241: spi: mpc52xx: fix use-after-free on registration failure
Noroxi assessment
Priority: Monitor (action score 31/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 336d9ad7560b3baba17af06727a888040ee93390, 5c77f11b9b5f1ad5a704dad875260c44016ede10, 8b49b6aadd0c622ca7d68b4a53ae10362e221cf3; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 336d9ad7560b3baba17af06727a888040ee93390, 5c77f11b9b5f1ad5a704dad875260c44016ede10, 8b49b6aadd0c622ca7d68b4a53ae10362e221cf3; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes 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: spi: mpc52xx: fix use-after-free on registration failure Make sure to disable and free the interrupts in case controller registration fails to avoid a potential use-after-free and resource leak. This issue was flagged by Sashiko when reviewing a controller deregistration fix.
- Published
- May 28, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-416
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 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.33 and later · before 6.12.90
- linux linux kernel6.13 and later · before 6.18.32
- linux linux kernel6.19 and later · before 7.0.9
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.33affected
- 42bbb70980f3720b0ae6da6af862af0e95a04351 and later · before b25eb3d24d03e571f09c04a0522c798ea35e48a1affected · git
- 42bbb70980f3720b0ae6da6af862af0e95a04351 and later · before dd74a790818ebb9a2be3a94ac935a374755cd278affected · git
- 42bbb70980f3720b0ae6da6af862af0e95a04351 and later · before 8b49b6aadd0c622ca7d68b4a53ae10362e221cf3affected · git
- 42bbb70980f3720b0ae6da6af862af0e95a04351 and later · before 336d9ad7560b3baba17af06727a888040ee93390affected · git
- 42bbb70980f3720b0ae6da6af862af0e95a04351 and later · before 5c77f11b9b5f1ad5a704dad875260c44016ede10affected · git
- 42bbb70980f3720b0ae6da6af862af0e95a04351 and later · before f62c060272b9d7423b1650b844e8e4e7b8f9f925affected · git
- before 2.6.33not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*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 | from 0 | — |
| Debian:13 | linux | before 6.12.90-1 | 6.12.90-1 |
| Debian:14 | linux | before 7.0.9-1 | 7.0.9-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-46230May 28, 2026 · drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg28Monitor
- ← EarlierCVE-2026-46234May 28, 2026 · vsock: fix buffer size clamping order31Monitor
- Later →CVE-2026-46242May 30, 2026 · eventpoll: fix ep_remove struct eventpoll / struct file UAF32Monitor
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 | 336d9ad7560b3baba17af06727a888040ee93390 | Vendor (CNA) |
| Linux Linux | 5c77f11b9b5f1ad5a704dad875260c44016ede10 | Vendor (CNA) |
| Linux Linux | 8b49b6aadd0c622ca7d68b4a53ae10362e221cf3 | Vendor (CNA) |
| Linux Linux | b25eb3d24d03e571f09c04a0522c798ea35e48a1 | Vendor (CNA) |
| Linux Linux | dd74a790818ebb9a2be3a94ac935a374755cd278 | Vendor (CNA) |
| Linux Linux | f62c060272b9d7423b1650b844e8e4e7b8f9f925 | Vendor (CNA) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.90-1 · Debian:13 | 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.
No history yet (it accumulates with the daily EPSS job).
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0290 · Jun 2, 2026(Linux Kernel Güvenlik Bildirimi)
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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 (5 more)Show less
- git.kernel.org/stable/c/5c77f11b9b5f1ad5a704dad875260c44016ede10
- git.kernel.org/stable/c/8b49b6aadd0c622ca7d68b4a53ae10362e221cf3
- git.kernel.org/stable/c/b25eb3d24d03e571f09c04a0522c798ea35e48a1
- git.kernel.org/stable/c/dd74a790818ebb9a2be3a94ac935a374755cd278
- git.kernel.org/stable/c/f62c060272b9d7423b1650b844e8e4e7b8f9f925
Vendor advisories and official records. Exploit/PoC links are deliberately left out.