CVE-2022-49967: bpf: Fix a data-race around bpf_jit_limit.
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.14% (FIRST EPSS).
- 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: Linux Linux 0947ae1121083d363d522ff7518ee72b55bd8d29, 4.10, 4.15.
Low priority for now. Upgrade to Linux Linux 0947ae1121083d363d522ff7518ee72b55bd8d29, 4.10, 4.15 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 a data-race around bpf_jit_limit. While reading bpf_jit_limit, it can be changed concurrently via sysctl, WRITE_ONCE() in __do_proc_doulongvec_minmax(). The size of bpf_jit_limit is long, so we need to add a paired READ_ONCE() to avoid load-tearing.
- Published
- Jun 18, 2025
- Updated
- Nov 5, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-362
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.1%
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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.9.190 and later · before 4.10
- linux linux kernel4.14.140 and later · before 4.15
- linux linux kernel4.19.47 and later · before 5.19.8
- linux linux kernel6.0
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
- c98446e1bab6253ddce7144cc2a91c400a323839, a1fe647042affe713a17243cd10e9b25f3d83948, 43caa29c99db5a41b204e8ced01b00e151335ca8, 4.20affected
- ede95a63b5e84ddeea6b0c473b36ab8bfd8c6ce3 and later · before ba632ad0bacb13197a8f38e7526448974e87f292affected · git
- ede95a63b5e84ddeea6b0c473b36ab8bfd8c6ce3 and later · before 0947ae1121083d363d522ff7518ee72b55bd8d29affected · git
- 4.9.190 and later · before 4.10affected · semver
- 4.14.140 and later · before 4.15affected · semver
- 4.19.47 and later · before 4.20affected · semver
- before 4.20not affected · semver
- 5.19.8 and later · up to and including 5.19.*not affected · semver
- 6.0 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.19.11-1 | 5.19.11-1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kernel-default | before 4.12.14-122.272.1 | 4.12.14-122.272.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_72 | before 1-8.3.1 | 1-8.3.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | kernel-source | before 4.12.14-122.272.1 | 4.12.14-122.272.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | kernel-syms | before 4.12.14-122.272.1 | 4.12.14-122.272.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-2022-49961Jun 18, 2025 · bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO28Monitor
- ← EarlierCVE-2022-49963Jun 18, 2025 · drm/i915/ttm: fix CCS handling22Monitor
- Later →CVE-2022-49970Jun 18, 2025 · bpf, cgroup: Fix kernel BUG in purge_effective_progs28Monitor
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 | 0947ae1121083d363d522ff7518ee72b55bd8d29 | Vendor (CNA) |
| Linux Linux | 4.10 | Vendor (CNA) |
| Linux Linux | 4.15 | Vendor (CNA) |
| Linux Linux | 4.20 | Vendor (CNA) |
| Linux Linux | ba632ad0bacb13197a8f38e7526448974e87f292 | Vendor (CNA) |
| debian:linux | 5.19.11-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-default | 4.12.14-122.272.1 · SUSE:Linux Enterprise Live Patching 12 SP5 | Package registry (OSV) |
| suse:kernel-source | 4.12.14-122.272.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
| suse:kernel-syms | 4.12.14-122.272.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
| suse:kgraft-patch-SLE12-SP5_Update_72 | 1-8.3.1 · SUSE:Linux Enterprise Live Patching 12 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.
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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:L/AC:H/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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.