CVE-2023-52462: bpf: fix check for attempt to corrupt spilled pointer
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.22% (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 2757f17972d87773b3677777f5682510f13c66ef, 40617d45ea05535105e202a8a819e388a2b1f036, 5.10.209.
Low priority for now. Upgrade to Linux Linux 2757f17972d87773b3677777f5682510f13c66ef, 40617d45ea05535105e202a8a819e388a2b1f036, 5.10.209 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: bpf: fix check for attempt to corrupt spilled pointer When register is spilled onto a stack as a 1/2/4-byte register, we set slot_type[BPF_REG_SIZE - 1] (plus potentially few more below it, depending on actual spill size). So to check if some stack slot has spilled register we need to consult slot_type[7], not slot_type[0]. To avoid the need to remember and double-check this in the future, just use is_spilled_reg() helper.
- Published
- Feb 23, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-476
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 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.
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.
Is your version affected? Check itNoroxi 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 |
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.16affected
- cdd73a5ed0840da88a3b9ad353f568e6f156d417 and later · before 2757f17972d87773b3677777f5682510f13c66efaffected · git
- 07c286c10a9cedbd71f20269ff3a4e73d9aab2fe and later · before 67e6707f07354ed1acb4e65552e97c60cf9d69cfaffected · git
- 27113c59b6d0a587b29ae72d4ff3f832f58b0651 and later · before fc3e3c50a0a4cac1463967c110686189e4a59104affected · git
- 27113c59b6d0a587b29ae72d4ff3f832f58b0651 and later · before 8dc15b0670594543c356567a1a45b0182ec63174affected · git
- 27113c59b6d0a587b29ae72d4ff3f832f58b0651 and later · before 40617d45ea05535105e202a8a819e388a2b1f036affected · git
- 27113c59b6d0a587b29ae72d4ff3f832f58b0651 and later · before ab125ed3ec1c10ccc36bc98c7a4256ad114a3daeaffected · git
- 5.10.163 and later · before 5.10.209affected · semver
- 5.15.86 and later · before 5.15.148affected · semver
- before 5.16not affected · semver
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 5.10.209
- linux linux kernel5.11.0 and later · before 5.15.148
- linux linux kernel5.16.0 and later · before 6.1.75
- linux linux kernel6.2.0 and later · before 6.6.14
- linux linux kernel6.7.0 and later · before 6.7.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:10 | linux-5.10 | before 5.10.209-2~deb10u1 | 5.10.209-2~deb10u1 |
| Debian:12 | linux | before 6.1.76-1 | 6.1.76-1 |
| Debian:13 | linux | before 6.6.15-1 | 6.6.15-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-52460Feb 23, 2024 · drm/amd/display: Fix NULL pointer dereference at hibernate22Monitor
- ← EarlierCVE-2023-52461Feb 23, 2024 · drm/sched: Fix bounds limiting when given a malformed entity31Monitor
- Later →CVE-2023-52463Feb 23, 2024 · efivarfs: force RO when remounting if SetVariable is not supported22Monitor
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 | 2757f17972d87773b3677777f5682510f13c66ef | Vendor (CNA) |
| Linux Linux | 40617d45ea05535105e202a8a819e388a2b1f036 | Vendor (CNA) |
| Linux Linux | 5.10.209 | Vendor (CNA) |
| Linux Linux | 5.15.148 | Vendor (CNA) |
| Linux Linux | 67e6707f07354ed1acb4e65552e97c60cf9d69cf | Vendor (CNA) |
| Linux Linux | 8dc15b0670594543c356567a1a45b0182ec63174 | Vendor (CNA) |
| Linux Linux | ab125ed3ec1c10ccc36bc98c7a4256ad114a3dae | Vendor (CNA) |
| Linux Linux | fc3e3c50a0a4cac1463967c110686189e4a59104 | Vendor (CNA) |
| debian:linux | 6.1.76-1 · Debian:12 | Package registry (OSV) |
| debian:linux-5.10 | 5.10.209-2~deb10u1 · Debian:10 | 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/40617d45ea05535105e202a8a819e388a2b1f036
- git.kernel.org/stable/c/67e6707f07354ed1acb4e65552e97c60cf9d69cf
- git.kernel.org/stable/c/8dc15b0670594543c356567a1a45b0182ec63174
- git.kernel.org/stable/c/ab125ed3ec1c10ccc36bc98c7a4256ad114a3dae
- git.kernel.org/stable/c/fc3e3c50a0a4cac1463967c110686189e4a59104
- lists.debian.org/debian-lts-announce/2024/06/msg00016.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.