perf/x86/intel/pt: Fix crash with stop filters in single-range mode
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.24% (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 1d9093457b243061a9bba23543c38726e864a643, 456f041e035913fcedb275aff6f8a71dfebcd394, e83d941fd3445f660d2f43647c580a320cc384f6.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1d9093457b243061a9bba23543c38726e864a643, 456f041e035913fcedb275aff6f8a71dfebcd394, e83d941fd3445f660d2f43647c580a320cc384f6 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: perf/x86/intel/pt: Fix crash with stop filters in single-range mode Add a check for !buf->single before calling pt_buffer_region_size in a place where a missing check can cause a kernel crash. Fixes a bug introduced by commit 670638477aed ("perf/x86/intel/pt: Opportunistically use single range output mode"), which added a support for PT single-range output mode. Since that commit if a PT stop filter range is hit while tracing, the kernel will crash because of a null pointer dereference in pt_handle_status due to calling pt_buffer_region_size without a ToPA configured. The commit which introduced single-range mode guarded almost all uses of the ToPA buffer variables with checks of the buf->single variable, but missed the case where tracing was stopped by the PT hardware, which happens when execution hits a configured stop filter. Tested that hitting a stop filter while PT recording successfully records a trace with this patch but crashes without this patch.
- Published
- Jun 20, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-476
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.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.
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.5 and later · before 5.10.99
- linux linux kernel5.11 and later · before 5.15.22
- linux linux kernel5.16 and later · before 5.16.8
- linux linux kernel5.17
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.5affected
- 670638477aede0d7a355ced04b569214aa3feacd and later · before 456f041e035913fcedb275aff6f8a71dfebcd394affected · git
- 670638477aede0d7a355ced04b569214aa3feacd and later · before e83d941fd3445f660d2f43647c580a320cc384f6affected · git
- 670638477aede0d7a355ced04b569214aa3feacd and later · before feffb6ae2c80b9a8206450cdef90f5943baced99affected · git
- 670638477aede0d7a355ced04b569214aa3feacd and later · before 1d9093457b243061a9bba23543c38726e864a643affected · git
- before 5.5not affected · semver
- 5.10.99 and later · up to and including 5.10.*not affected · semver
- 5.15.22 and later · up to and including 5.15.*not affected · semver
- 5.16.8 and later · up to and including 5.16.*not affected · semver
- 5.17 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 5.16.10-1 | 5.16.10-1 |
| openSUSE:Leap 15.5 | kernel-azure | before 5.14.21-150500.33.63.1 | 5.14.21-150500.33.63.1 |
| openSUSE:Leap 15.5 | kernel-rt_debug | before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
| openSUSE:Leap 15.5 | kernel-source-azure | before 5.14.21-150500.33.63.1 | 5.14.21-150500.33.63.1 |
| openSUSE:Leap 15.5 | kernel-source-rt | before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
| openSUSE:Leap 15.5 | kernel-syms-azure | before 5.14.21-150500.33.63.1 | 5.14.21-150500.33.63.1 |
| openSUSE:Leap 15.5 | kernel-syms-rt | before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
| openSUSE:Leap Micro 5.5 | kernel-rt | before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5-RT_Update_18 | before 1-150500.11.3.1 | 1-150500.11.3.1 |
| SUSE:Linux Enterprise Micro 5.5 | kernel-rt | before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
| SUSE:Linux Enterprise Micro 5.5 | kernel-source-rt | before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP5 | kernel-azure | before 5.14.21-150500.33.63.1 | 5.14.21-150500.33.63.1 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP5 | kernel-source-azure | before 5.14.21-150500.33.63.1 | 5.14.21-150500.33.63.1 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP5 | kernel-syms-azure | before 5.14.21-150500.33.63.1 | 5.14.21-150500.33.63.1 |
| SUSE:Real Time Module 15 SP5 | kernel-rt_debug | before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
| SUSE:Real Time Module 15 SP5 | kernel-syms-rt | before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.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-48711Jun 20, 2024 · tipc: improve size validations for received domain records22Monitor
- ← EarlierCVE-2022-48712Jun 20, 2024 · ext4: fix error handling in ext4_fc_record_modified_inode()31Monitor
- Later →CVE-2022-48714Jun 20, 2024 · bpf: Use VM_MAP instead of VM_ALLOC for ringbuf28Monitor
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 | 1d9093457b243061a9bba23543c38726e864a643 | Vendor (CNA) |
| Linux Linux | 456f041e035913fcedb275aff6f8a71dfebcd394 | Vendor (CNA) |
| Linux Linux | e83d941fd3445f660d2f43647c580a320cc384f6 | Vendor (CNA) |
| Linux Linux | feffb6ae2c80b9a8206450cdef90f5943baced99 | Vendor (CNA) |
| debian:linux | 5.16.10-1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-azure | 5.14.21-150500.33.63.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-rt | 5.14.21-150500.13.64.1 · openSUSE:Leap Micro 5.5 | Package registry (OSV) |
| opensuse:kernel-rt_debug | 5.14.21-150500.13.64.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-source-azure | 5.14.21-150500.33.63.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-source-rt | 5.14.21-150500.13.64.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-syms-azure | 5.14.21-150500.33.63.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-syms-rt | 5.14.21-150500.13.64.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| suse:kernel-azure | 5.14.21-150500.33.63.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP5 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP5-RT_Update_18 | 1-150500.11.3.1 · SUSE:Linux Enterprise Live Patching 15 SP5 | Package registry (OSV) |
| suse:kernel-rt | 5.14.21-150500.13.64.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:kernel-rt_debug | 5.14.21-150500.13.64.1 · SUSE:Real Time Module 15 SP5 | Package registry (OSV) |
| suse:kernel-source-azure | 5.14.21-150500.33.63.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP5 | Package registry (OSV) |
| suse:kernel-source-rt | 5.14.21-150500.13.64.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:kernel-syms-azure | 5.14.21-150500.33.63.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP5 | Package registry (OSV) |
| suse:kernel-syms-rt | 5.14.21-150500.13.64.1 · SUSE:Real Time Module 15 SP5 | 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0733 · Jun 24, 2024(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.
- 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-476 · NULL Pointer DereferenceCVSS 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 (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.