CVE-2024-57979: pps: Fix a use-after-free
Noroxi assessment
Priority: Monitor (action score 31/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.26% (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 1a7735ab2cb9747518a7416fb5929e85442dec62, 3.3, 3.5; cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.0 5.15.180.1-1; cbl2 kernel 5.15.176.3-3 on CBL-Mariner 2.0 5.15.180.1-1.
Low priority for now. Upgrade to Linux Linux 1a7735ab2cb9747518a7416fb5929e85442dec62, 3.3, 3.5; cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.0 5.15.180.1-1; cbl2 kernel 5.15.176.3-3 on CBL-Mariner 2.0 5.15.180.1-1 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: pps: Fix a use-after-free On a board running ntpd and gpsd, I'm seeing a consistent use-after-free in sys_exit() from gpsd when rebooting: pps pps1: removed ------------[ cut here ]------------ kobject: '(null)' (00000000db4bec24): is not initialized, yet kobject_put() is being called. WARNING: CPU: 2 PID: 440 at lib/kobject.c:734 kobject_put+0x120/0x150 CPU: 2 UID: 299 PID: 440 Comm: gpsd Not tainted 6.11.0-rc6-00308-gb31c44928842 #1 Hardware name: Raspberry Pi 4 Model B Rev 1.1 (DT) pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : kobject_put+0x120/0x150 lr : kobject_put+0x120/0x150 sp : ffffffc0803d3ae0 x29: ffffffc0803d3ae0 x28: ffffff8042dc9738 x27: 0000000000000001 x26: 0000000000000000 x25: ffffff8042dc9040 x24: ffffff8042dc9440 x23: ffffff80402a4620 x22: ffffff8042ef4bd0 x21: ffffff80405cb600 x20: 000000000008001b x19: ffffff8040b3b6e0 x18: 0000000000000000 x17: 0000000000000000 x16: 0000000000000000 x15: 696e6920746f6e20 x14: 7369203a29343263 x13: 205d303434542020 x12: 0000000000000000 x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000 x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000 x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000 x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000 Call trace: kobject_put+0x120/0x150 cdev_put+0x20/0x3c __fput+0x2c4/0x2d8 ____fput+0x1c/0x38 task_work_run+0x70/0xfc do_exit+0x2a0/0x924 do_group_exit+0x34/0x90 get_signal+0x7fc/0x8c0 do_signal+0x128/0x13b4 do_notify_resume+0xdc/0x160 el0_svc+0xd4/0xf8 el0t_64_sync_handler+0x140/0x14c el0t_64_sync+0x190/0x194 ---[ end trace 0000000000000000 ]--- ...followed by more symptoms of corruption, with similar stacks: refcount_t: underflow; use-after-free. kernel BUG at lib/list_debug.c:62! Kernel panic - not syncing: Oops - BUG: Fatal exception This happens because pps_device_destruct() frees the pps_device with the embedded cdev immediately after calling cdev_del(), but, as the comment above cdev_del() notes, fops for previously opened cdevs are still callable even after cdev_del() returns. I think this bug has always been there: I can't explain why it suddenly started happening every time I reboot this particular board. In commit d953e0e837e6 ("pps: Fix a use-after free bug when unregistering a source."), George Spelvin suggested removing the embedded cdev. That seems like the simplest way to fix this, so I've implemented his suggestion, using __register_chrdev() with pps_idr becoming the source of truth for which minor corresponds to which device. But now that pps_idr defines userspace visibility instead of cdev_add(), we need to be sure the pps->dev refcount can't reach zero while userspace can still find it again. So, the idr_remove() call moves to pps_unregister_cdev(), and pps_idr now holds a reference to pps->dev. pps_core: source serial1 got cdev (251:1) <...> pps pps1: removed pps_core: unregistering pps1 pps_core: deallocating pps1
- Published
- Feb 27, 2025
- Updated
- Oct 15, 2026
- EPSS
- 0.2% · 19th percentile
- CWE
- CWE-416
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel3.2.40 and later · before 3.3
- linux linux kernel3.4.87 and later · before 3.5
- linux linux kernel3.8.1 and later · before 5.4.291
- linux linux kernel5.5 and later · before 5.10.235
- linux linux kernel5.11 and later · before 5.15.179
- linux linux kernel5.16 and later · before 6.1.129
- linux linux kernel6.2 and later · before 6.6.76
- linux linux kernel6.7 and later · before 6.12.13
- linux linux kernel6.13 and later · before 6.13.2
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
- 77327a71f9841b7dfa708195d1cb133d4ef4a989, cd59fb14918a6b20c1ac8be121fa6397b97b00cb, 49626fbb0360332e40fd76a48cb2ba876d6134ad, 3.9affected
- d953e0e837e65ecc1ddaa4f9560f7925878a0de6 and later · before 785c78ed0d39d1717cca3ef931d3e51337b5e90eaffected · git
- d953e0e837e65ecc1ddaa4f9560f7925878a0de6 and later · before 1a7735ab2cb9747518a7416fb5929e85442dec62affected · git
- d953e0e837e65ecc1ddaa4f9560f7925878a0de6 and later · before c4041b6b0a7a3def8cf3f3d6120ff337bc4c40f7affected · git
- d953e0e837e65ecc1ddaa4f9560f7925878a0de6 and later · before 91932db1d96b2952299ce30c1c693d834d10ace6affected · git
- d953e0e837e65ecc1ddaa4f9560f7925878a0de6 and later · before cd3bbcb6b3a7caa5ce67de76723b6d8531fb7f64affected · git
- d953e0e837e65ecc1ddaa4f9560f7925878a0de6 and later · before 7e5ee3281dc09014367f5112b6d566ba36ea2d49affected · git
- d953e0e837e65ecc1ddaa4f9560f7925878a0de6 and later · before 85241f7de216f8298f6e48540ea13d7dcd100870affected · git
- d953e0e837e65ecc1ddaa4f9560f7925878a0de6 and later · before c79a39dc8d060b9e64e8b0fa9d245d44befeefbeaffected · git
- 3.2.40 and later · before 3.3affected · semver
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-553.44.1.el8_10 | 4.18.0-553.44.1.el8_10 |
| AlmaLinux:8 | kernel | before 4.18.0-553.44.1.el8_10 | 4.18.0-553.44.1.el8_10 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-553.44.1.el8_10 | 4.18.0-553.44.1.el8_10 |
| AlmaLinux:8 | kernel-core | before 4.18.0-553.44.1.el8_10 | 4.18.0-553.44.1.el8_10 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-553.44.1.el8_10 | 4.18.0-553.44.1.el8_10 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-553.44.1.el8_10 | 4.18.0-553.44.1.el8_10 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-553.44.1.el8_10 | 4.18.0-553.44.1.el8_10 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-553.44.1.el8_10 | 4.18.0-553.44.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-553.44.1.el8_10 | 4.18.0-553.44.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-553.44.1.el8_10 | 4.18.0-553.44.1.el8_10 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-553.44.1.el8_10 | 4.18.0-553.44.1.el8_10 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-553.44.1.el8_10 | 4.18.0-553.44.1.el8_10 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-553.44.1.el8_10 | 4.18.0-553.44.1.el8_10 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-553.44.1.el8_10 | 4.18.0-553.44.1.el8_10 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-553.44.1.el8_10 | 4.18.0-553.44.1.el8_10 |
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.44.1.rt7.385.el8_10 | 4.18.0-553.44.1.rt7.385.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.44.1.rt7.385.el8_10 | 4.18.0-553.44.1.rt7.385.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.44.1.rt7.385.el8_10 | 4.18.0-553.44.1.rt7.385.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.44.1.rt7.385.el8_10 | 4.18.0-553.44.1.rt7.385.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.44.1.rt7.385.el8_10 | 4.18.0-553.44.1.rt7.385.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.44.1.rt7.385.el8_10 | 4.18.0-553.44.1.rt7.385.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.44.1.rt7.385.el8_10 | 4.18.0-553.44.1.rt7.385.el8_10 |
| AlmaLinux:8 | kernel-rt-devel | before 4.18.0-553.44.1.rt7.385.el8_10 | 4.18.0-553.44.1.rt7.385.el8_10 |
| AlmaLinux:8 | kernel-rt-modules | before 4.18.0-553.44.1.rt7.385.el8_10 | 4.18.0-553.44.1.rt7.385.el8_10 |
+65
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-57976Feb 27, 2025 · btrfs: do proper folio cleanup when cow_file_range() failed22Monitor
- ← EarlierCVE-2024-57977Feb 27, 2025 · memcg: fix soft lockup in the OOM process22Monitor
- Later →CVE-2024-57980Feb 27, 2025 · media: uvcvideo: Fix double free in error path31Monitor
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 | 1a7735ab2cb9747518a7416fb5929e85442dec62 | Vendor (CNA) |
| Linux Linux | 3.3 | Vendor (CNA) |
| Linux Linux | 3.5 | Vendor (CNA) |
| Linux Linux | 3.9 | Vendor (CNA) |
| Linux Linux | 785c78ed0d39d1717cca3ef931d3e51337b5e90e | Vendor (CNA) |
| Linux Linux | 7e5ee3281dc09014367f5112b6d566ba36ea2d49 | Vendor (CNA) |
| Linux Linux | 85241f7de216f8298f6e48540ea13d7dcd100870 | Vendor (CNA) |
| Linux Linux | 91932db1d96b2952299ce30c1c693d834d10ace6 | Vendor (CNA) |
| Linux Linux | c4041b6b0a7a3def8cf3f3d6120ff337bc4c40f7 | Vendor (CNA) |
| Linux Linux | c79a39dc8d060b9e64e8b0fa9d245d44befeefbe | Vendor (CNA) |
| Linux Linux | cd3bbcb6b3a7caa5ce67de76723b6d8531fb7f64 | Vendor (CNA) |
| cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.0 | 5.15.180.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.176.3-3 on CBL-Mariner 2.0 | 5.15.180.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.180.1-1 on CBL Mariner 2.0 | 5.15.180.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:bpftool | 4.18.0-553.44.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.44.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 4.18.0-553.44.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-core | 4.18.0-553.44.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-cross-headers | 4.18.0-553.44.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug | 4.18.0-553.44.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-core | 4.18.0-553.44.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-devel | 4.18.0-553.44.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules | 4.18.0-553.44.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules-extra | 4.18.0-553.44.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-devel | 4.18.0-553.44.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-doc | 4.18.0-553.44.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.129-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.1 | 6.1.129-1~deb11u1 · Debian:11 | Package registry (OSV) |
| red hat:bpftool | 0:4.18.0-553.44.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:4.18.0-553.44.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
+12
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.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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 (13 more)Show less
- git.kernel.org/stable/c/785c78ed0d39d1717cca3ef931d3e51337b5e90e
- git.kernel.org/stable/c/7e5ee3281dc09014367f5112b6d566ba36ea2d49
- git.kernel.org/stable/c/85241f7de216f8298f6e48540ea13d7dcd100870
- git.kernel.org/stable/c/91932db1d96b2952299ce30c1c693d834d10ace6
- git.kernel.org/stable/c/c4041b6b0a7a3def8cf3f3d6120ff337bc4c40f7
- git.kernel.org/stable/c/c79a39dc8d060b9e64e8b0fa9d245d44befeefbe
- git.kernel.org/stable/c/cd3bbcb6b3a7caa5ce67de76723b6d8531fb7f64
- lists.debian.org/debian-lts-announce/2025/03/msg00028.html
- lists.debian.org/debian-lts-announce/2025/05/msg00030.html
- cert-portal.siemens.com/productcert/html/ssa-019113.html
- cert-portal.siemens.com/productcert/html/ssa-265688.html
- cert-portal.siemens.com/productcert/html/ssa-457936.html
- cert-portal.siemens.com/productcert/html/ssa-784472.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.