CVE-2024-49888: bpf: Fix a sdiv overflow issue
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.28% (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 45f2bbe7bc08d716a07a40025c672cad93180903, 4902a6a0dc593c82055fc8c9ada371bafe26c9cc, 7dd34d7b7dcf9309fc6224caf4dd5b35bedddcb7.
Low priority for now. Upgrade to Linux Linux 45f2bbe7bc08d716a07a40025c672cad93180903, 4902a6a0dc593c82055fc8c9ada371bafe26c9cc, 7dd34d7b7dcf9309fc6224caf4dd5b35bedddcb7 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 sdiv overflow issue Zac Ecob reported a problem where a bpf program may cause kernel crash due to the following error: Oops: divide error: 0000 [#1] PREEMPT SMP KASAN PTI The failure is due to the below signed divide: LLONG_MIN/-1 where LLONG_MIN equals to -9,223,372,036,854,775,808. LLONG_MIN/-1 is supposed to give a positive number 9,223,372,036,854,775,808, but it is impossible since for 64-bit system, the maximum positive number is 9,223,372,036,854,775,807. On x86_64, LLONG_MIN/-1 will cause a kernel exception. On arm64, the result for LLONG_MIN/-1 is LLONG_MIN. Further investigation found all the following sdiv/smod cases may trigger an exception when bpf program is running on x86_64 platform: - LLONG_MIN/-1 for 64bit operation - INT_MIN/-1 for 32bit operation - LLONG_MIN%-1 for 64bit operation - INT_MIN%-1 for 32bit operation where -1 can be an immediate or in a register. On arm64, there are no exceptions: - LLONG_MIN/-1 = LLONG_MIN - INT_MIN/-1 = INT_MIN - LLONG_MIN%-1 = 0 - INT_MIN%-1 = 0 where -1 can be an immediate or in a register. Insn patching is needed to handle the above cases and the patched codes produced results aligned with above arm64 result. The below are pseudo codes to handle sdiv/smod exceptions including both divisor -1 and divisor 0 and the divisor is stored in a register. sdiv: tmp = rX tmp += 1 /* [-1, 0] -> [0, 1] if tmp >(unsigned) 1 goto L2 if tmp == 0 goto L1 rY = 0 L1: rY = -rY; goto L3 L2: rY /= rX L3: smod: tmp = rX tmp += 1 /* [-1, 0] -> [0, 1] if tmp >(unsigned) 1 goto L1 if tmp == 1 (is64 ? goto L2 : goto L3) rY = 0; goto L2 L1: rY %= rX L2: goto L4 // only when !is64 L3: wY = wY // only when !is64 L4: [1] https://lore.kernel.org/bpf/tPJLTEh7S_DxFEqAI2Ji5MBSoZVg7_G-Py2iaZpAaWtM961fFTWtsnlzwvTbzBzaUzwQAoNATXKUlt0LZOFgnDcIyKCswAnAGdUF3LBrhGQ=@protonmail.com/
- Published
- Oct 21, 2024
- Updated
- Oct 21, 2026
- EPSS
- 0.2% · 20th percentile
- CWE
- CWE-190
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 kernelbefore 6.10.14
- linux linux kernel6.11 and later · before 6.11.3
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
- 6.6affected
- ec0e2da95f72d4a46050a4d994e4fe471474fd80 and later · before 45f2bbe7bc08d716a07a40025c672cad93180903affected · git
- ec0e2da95f72d4a46050a4d994e4fe471474fd80 and later · before 4902a6a0dc593c82055fc8c9ada371bafe26c9ccaffected · git
- ec0e2da95f72d4a46050a4d994e4fe471474fd80 and later · before d22e45a369afc7c28f11acfa5b5e8e478227ca5daffected · git
- ec0e2da95f72d4a46050a4d994e4fe471474fd80 and later · before 7dd34d7b7dcf9309fc6224caf4dd5b35bedddcb7affected · git
- before 6.6not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
- 6.10.14 and later · up to and including 6.10.*not affected · semver
- 6.11.3 and later · up to and including 6.11.*not affected · semver
- 6.12 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 |
|---|---|---|---|
| AlmaLinux:9 | bpftool | before 7.4.0-503.19.1.el9_5 | 7.4.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel-core | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
| AlmaLinux:9 | kernel-debug-modules | before 5.14.0-503.19.1.el9_5 | 5.14.0-503.19.1.el9_5 |
+96
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-2024-49884Oct 21, 2024 · ext4: fix slab-use-after-free in ext4_split_extent_at()31Monitor
- ← EarlierCVE-2024-49885Oct 21, 2024 · mm, slub: avoid zeroing kmalloc redzone22Monitor
- Later →CVE-2024-49889Oct 21, 2024 · ext4: avoid use-after-free in ext4_ext_show_leaf()31Monitor
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 | 45f2bbe7bc08d716a07a40025c672cad93180903 | Vendor (CNA) |
| Linux Linux | 4902a6a0dc593c82055fc8c9ada371bafe26c9cc | Vendor (CNA) |
| Linux Linux | 7dd34d7b7dcf9309fc6224caf4dd5b35bedddcb7 | Vendor (CNA) |
| Linux Linux | d22e45a369afc7c28f11acfa5b5e8e478227ca5d | Vendor (CNA) |
| almalinux:bpftool | 7.4.0-503.19.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel | 5.14.0-503.19.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-503.19.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-503.19.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-503.19.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-503.19.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-503.19.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-503.19.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-503.19.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-503.19.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-503.19.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-503.19.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.11.4-1 · Debian:13 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.3.0-427.48.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-427.48.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-427.48.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-427.48.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-427.48.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-427.48.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-427.48.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-427.48.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-427.48.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-427.48.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-427.48.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-427.48.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | 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.
- CVE-2026-23457529 days apartnetfilter: nf_conntrack_sip: fix Content-Length u32 truncation in sip_help_tcp()34Monitor
- CVE-2022-490300 days apartlibbpf: Handle size overflow for ringbuf mmap31Monitor
- CVE-2024-4213683 days apartcdrom: rearrange last_media_change check to avoid unintentional overflow31Monitor
- CVE-2022-4883797 days apartusb: gadget: rndis: prevent integer overflow in rndis_set_response()31Monitor
- CVE-2024-40994101 days apartptp: fix integer overflow in max_vclocks_store31Monitor
- CVE-2024-41000101 days apartblock/ioctl: prefer different overflow check31Monitor
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
- 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-190 · Integer Overflow or WraparoundCVSS 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.
Attack patterns (CAPEC)
ATT&CK techniques
—
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.