CVE-2023-52483: mctp: perform route lookups under a RCU read-side lock
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.23% (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 1db0724a01b558feb1ecae551782add1951a114a, 2405f64a95a7a094eb24cba9bcfaffd1ea264de4, 5093bbfc10ab6636b32728e35813cbd79feb063c.
Low priority for now. Upgrade to Linux Linux 1db0724a01b558feb1ecae551782add1951a114a, 2405f64a95a7a094eb24cba9bcfaffd1ea264de4, 5093bbfc10ab6636b32728e35813cbd79feb063c 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: mctp: perform route lookups under a RCU read-side lock Our current route lookups (mctp_route_lookup and mctp_route_lookup_null) traverse the net's route list without the RCU read lock held. This means the route lookup is subject to preemption, resulting in an potential grace period expiry, and so an eventual kfree() while we still have the route pointer. Add the proper read-side critical section locks around the route lookups, preventing premption and a possible parallel kfree. The remaining net->mctp.routes accesses are already under a rcu_read_lock, or protected by the RTNL for updates. Based on an analysis from Sili Luo <rootlab@huawei.com>, where introducing a delay in the route lookup could cause a UAF on simultaneous sendmsg() and route deletion.
- Published
- Feb 29, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 14th 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.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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 kernel5.15 and later · before 5.15.137
- linux linux kernel5.16 and later · before 6.1.59
- linux linux kernel6.2 and later · before 6.5.8
- linux linux kernel6.6
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.15affected
- 889b7da23abf92faf34491df95733bda63639e32 and later · before 6c52b12159049046483fdb0c411a0a1869c41a67affected · git
- 889b7da23abf92faf34491df95733bda63639e32 and later · before 1db0724a01b558feb1ecae551782add1951a114aaffected · git
- 889b7da23abf92faf34491df95733bda63639e32 and later · before 2405f64a95a7a094eb24cba9bcfaffd1ea264de4affected · git
- 889b7da23abf92faf34491df95733bda63639e32 and later · before 5093bbfc10ab6636b32728e35813cbd79feb063caffected · git
- before 5.15not affected · semver
- 5.15.137 and later · up to and including 5.15.*not affected · semver
- 6.1.59 and later · up to and including 6.1.*not affected · semver
- 6.5.8 and later · up to and including 6.5.*not affected · semver
- 6.6 and laternot affected · original_commit_for_fix
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.64-1 | 6.1.64-1 |
| Debian:13 | linux | before 6.5.8-1 | 6.5.8-1 |
| openSUSE:Leap 15.6 | kernel-azure | before 6.4.0-150600.8.5.4 | 6.4.0-150600.8.5.4 |
| openSUSE:Leap 15.6 | kernel-source-azure | before 6.4.0-150600.8.5.4 | 6.4.0-150600.8.5.4 |
| openSUSE:Leap 15.6 | kernel-syms-azure | before 6.4.0-150600.8.5.1 | 6.4.0-150600.8.5.1 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | kernel-azure | before 6.4.0-150600.8.5.4 | 6.4.0-150600.8.5.4 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | kernel-source-azure | before 6.4.0-150600.8.5.4 | 6.4.0-150600.8.5.4 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | kernel-syms-azure | before 6.4.0-150600.8.5.1 | 6.4.0-150600.8.5.1 |
| SUSE:Linux Micro 6.0 | kernel-default | before 6.4.0-18.1 | 6.4.0-18.1 |
| SUSE:Linux Micro 6.0 | kernel-default-base | before 6.4.0-17.1.1.51 | 6.4.0-17.1.1.51 |
| SUSE:Linux Micro 6.0 | kernel-kvmsmall | before 6.4.0-18.1 | 6.4.0-18.1 |
| SUSE:Linux Micro 6.0 | kernel-rt | before 6.4.0-9.1 | 6.4.0-9.1 |
| SUSE:Linux Micro 6.0 | kernel-source | before 6.4.0-18.1 | 6.4.0-18.1 |
| SUSE:Linux Micro 6.0 | kernel-source-rt | before 6.4.0-9.1 | 6.4.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-2023-52481Feb 29, 2024 · arm64: errata: Add Cortex-A520 speculative unprivileged load workaround18Monitor
- ← EarlierCVE-2023-52482Feb 29, 2024 · x86/srso: Add SRSO mitigation for Hygon processors31Monitor
- Later →CVE-2023-52484Feb 29, 2024 · iommu/arm-smmu-v3: Fix soft lockup triggered by arm_smmu_mm_invalidate_range22Monitor
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 | 1db0724a01b558feb1ecae551782add1951a114a | Vendor (CNA) |
| Linux Linux | 2405f64a95a7a094eb24cba9bcfaffd1ea264de4 | Vendor (CNA) |
| Linux Linux | 5093bbfc10ab6636b32728e35813cbd79feb063c | Vendor (CNA) |
| Linux Linux | 6c52b12159049046483fdb0c411a0a1869c41a67 | Vendor (CNA) |
| debian:linux | 6.1.64-1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-azure | 6.4.0-150600.8.5.4 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-source-azure | 6.4.0-150600.8.5.4 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-syms-azure | 6.4.0-150600.8.5.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:kernel-azure | 6.4.0-150600.8.5.4 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | Package registry (OSV) |
| suse:kernel-default | 6.4.0-18.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-default-base | 6.4.0-17.1.1.51 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-kvmsmall | 6.4.0-18.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-rt | 6.4.0-9.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-source | 6.4.0-18.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-source-azure | 6.4.0-150600.8.5.4 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | Package registry (OSV) |
| suse:kernel-source-rt | 6.4.0-9.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-syms-azure | 6.4.0-150600.8.5.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | 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).
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 (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.