Spectre V1 Gadget in do_prlimit in the Linux Kernel
Noroxi assessment
Priority: Monitor (action score 18/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.72% (FIRST EPSS); higher than 52.9% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: bpftool (AlmaLinux:8) 4.18.0-513.5.1.el8_9; kernel (AlmaLinux:8) 4.18.0-513.5.1.el8_9; kernel-abi-stablelists (AlmaLinux:8) 4.18.0-513.5.1.el8_9.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to bpftool (AlmaLinux:8) 4.18.0-513.5.1.el8_9; kernel (AlmaLinux:8) 4.18.0-513.5.1.el8_9; kernel-abi-stablelists (AlmaLinux:8) 4.18.0-513.5.1.el8_9 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
A speculative pointer dereference problem exists in the Linux Kernel on the do_prlimit() function. The resource argument value is controlled and is used in pointer arithmetic for the 'rlim' variable and can be used to leak the contents. We recommend upgrading past version 6.1.8 or commit 739790605705ddcf18f21782b9c99ad7d53a8c11
- Published
- Apr 26, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.7% · 52th percentile
- CWE
- CWE-476
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 4.7
- CNA · Google
- 5.3
- 0.6 point gap
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
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 |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- linux linux kernelbefore 6.1.8
- linux linux kernel6.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Google). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux Kernel
- up to and including 6.1.8affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | bpftool | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-core | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-tools | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-tools-libs | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-tools-libs-devel | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-zfcpdump | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-zfcpdump-core | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-zfcpdump-devel | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-zfcpdump-modules | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | kernel-zfcpdump-modules-extra | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
| AlmaLinux:8 | perf | before 4.18.0-513.5.1.el8_9 | 4.18.0-513.5.1.el8_9 |
+96
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-2023-0045Apr 25, 2023 · Incorrect indirect branch prediction barrier in the Linux Kernel31Monitor
- ← EarlierCVE-2023-2269Apr 25, 2023 · A denial of service problem was found, due to a possible recursive locking scenario, resulting in a deadlock in table_clear in drivers/md/dm17Monitor
- Later →CVE-2023-31436Apr 28, 2023 · qfq_change_class in net/sched/sch_qfq.c in the Linux kernel before 6.2.13 allows an out-of-bounds write because lmax can exceed QFQ_MIN_LMAX31Monitor
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 |
|---|---|---|
| almalinux:bpftool | 7.0.0-284.25.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel | 5.14.0-284.25.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-284.25.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-284.25.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-284.25.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-284.25.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-284.25.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-284.25.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-284.25.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-284.25.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-284.25.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-284.25.1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.1.8-1 · Debian:12 | Package registry (OSV) |
| debian:linux-5.10 | 5.10.178-3~deb10u1 · Debian:10 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.0.0-284.25.1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-284.25.1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-284.25.1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-284.25.1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-284.25.1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-284.25.1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-284.25.1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-284.25.1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-284.25.1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-284.25.1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-284.25.1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-284.25.1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| rocky linux:kernel-rt | 0:5.14.0-284.25.1.rt14.310.el9_2 · Rocky Linux:9 | 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.
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-23-0391 · Jul 10, 2023(Linux Kernel Güncellemesi)
- TR-23-0271 · May 17, 2023(Linux Kernel Güncellemesi)
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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/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
- 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.