CVE-2024-36899: gpiolib: cdev: Fix use after free in lineinfo_changed_notify
Noroxi assessment
Priority: Monitor (action score 28/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.17% (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 02f6b0e1ec7e0e7d059dddc893645816552039da, 2d008d4961b039d2edce8976289773961b7e5fb5, 2dfbb920a89bdc58087672ad5325dc6c588b6860; cbl2 kernel 5.15.179.1-1 on CBL Mariner 2.0 5.15.179.1-1; cbl2 kernel 5.15.182.1-1 on CBL Mariner 2.0 CBL-Mariner Releases.
Low priority for now. Upgrade to Linux Linux 02f6b0e1ec7e0e7d059dddc893645816552039da, 2d008d4961b039d2edce8976289773961b7e5fb5, 2dfbb920a89bdc58087672ad5325dc6c588b6860; cbl2 kernel 5.15.179.1-1 on CBL Mariner 2.0 5.15.179.1-1; cbl2 kernel 5.15.182.1-1 on CBL Mariner 2.0 CBL-Mariner Releases 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: gpiolib: cdev: Fix use after free in lineinfo_changed_notify The use-after-free issue occurs as follows: when the GPIO chip device file is being closed by invoking gpio_chrdev_release(), watched_lines is freed by bitmap_free(), but the unregistration of lineinfo_changed_nb notifier chain failed due to waiting write rwsem. Additionally, one of the GPIO chip's lines is also in the release process and holds the notifier chain's read rwsem. Consequently, a race condition leads to the use-after-free of watched_lines. Here is the typical stack when issue happened: [free] gpio_chrdev_release() --> bitmap_free(cdev->watched_lines) <-- freed --> blocking_notifier_chain_unregister() --> down_write(&nh->rwsem) <-- waiting rwsem --> __down_write_common() --> rwsem_down_write_slowpath() --> schedule_preempt_disabled() --> schedule() [use] st54spi_gpio_dev_release() --> gpio_free() --> gpiod_free() --> gpiod_free_commit() --> gpiod_line_state_notify() --> blocking_notifier_call_chain() --> down_read(&nh->rwsem); <-- held rwsem --> notifier_call_chain() --> lineinfo_changed_notify() --> test_bit(xxxx, cdev->watched_lines) <-- use after free The side effect of the use-after-free issue is that a GPIO line event is being generated for userspace where it shouldn't. However, since the chrdev is being closed, userspace won't have the chance to read that event anyway. To fix the issue, call the bitmap_free() function after the unregistration of lineinfo_changed_nb notifier chain.
- BDU:2024-04554
- ALSA-2024:6997
- DLA-4075-1
- DLA-4076-1
- DSA-5860-1
- RHSA-2024:6997
- RHSA-2024:7004
- RHSA-2024:7005
- SUSE-SU-2024:2385-1
- SUSE-SU-2024:2495-1
- SUSE-SU-2024:3623-1
- SUSE-SU-2024:3624-1
- SUSE-SU-2024:3625-1
- SUSE-SU-2024:3628-1
- SUSE-SU-2024:3631-1
- SUSE-SU-2024:3632-1
- SUSE-SU-2024:3635-1
- SUSE-SU-2024:3636-1
- SUSE-SU-2024:3638-1
- SUSE-SU-2024:3639-1
- Published
- May 30, 2024
- Updated
- Oct 15, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-362
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.0 / 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.
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.7 and later · before 6.6.31
- linux linux kernel6.7 and later · before 6.8.10
- linux linux kernel6.9
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.7affected
- 51c1064e82e77b39a49889287ca50709303e2f26 and later · before 2dfbb920a89bdc58087672ad5325dc6c588b6860affected · git
- 51c1064e82e77b39a49889287ca50709303e2f26 and later · before 2d008d4961b039d2edce8976289773961b7e5fb5affected · git
- 51c1064e82e77b39a49889287ca50709303e2f26 and later · before d38c49f7bdf14381270736299e2ff68ec248a017affected · git
- 51c1064e82e77b39a49889287ca50709303e2f26 and later · before 95ca7c90eaf5ea8a8460536535101e3e81160e2aaffected · git
- 51c1064e82e77b39a49889287ca50709303e2f26 and later · before ca710b5f40b8b16fdcad50bebd47f50e4c62d239affected · git
- 51c1064e82e77b39a49889287ca50709303e2f26 and later · before 02f6b0e1ec7e0e7d059dddc893645816552039daaffected · git
- before 5.7not affected · semver
- 5.10.234 and later · up to and including 5.10.*not affected · semver
- 5.15.177 and later · up to and including 5.15.*not affected · semver
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.3.0-427.37.1.el9_4 | 7.3.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel-core | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
| AlmaLinux:9 | kernel-debug-modules | before 5.14.0-427.37.1.el9_4 | 5.14.0-427.37.1.el9_4 |
+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-36020May 30, 2024 · i40e: fix vf may be used uninitialized in this function warning22Monitor
- ← EarlierCVE-2024-36894May 30, 2024 · usb: gadget: f_fs: Fix race between aio_cancel() and AIO request complete31Monitor
- Later →CVE-2024-36902May 30, 2024 · ipv6: fib6_rules: avoid possible NULL dereference in fib6_rule_action()22Monitor
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 | 02f6b0e1ec7e0e7d059dddc893645816552039da | Vendor (CNA) |
| Linux Linux | 2d008d4961b039d2edce8976289773961b7e5fb5 | Vendor (CNA) |
| Linux Linux | 2dfbb920a89bdc58087672ad5325dc6c588b6860 | Vendor (CNA) |
| Linux Linux | 95ca7c90eaf5ea8a8460536535101e3e81160e2a | Vendor (CNA) |
| Linux Linux | ca710b5f40b8b16fdcad50bebd47f50e4c62d239 | Vendor (CNA) |
| Linux Linux | d38c49f7bdf14381270736299e2ff68ec248a017 | Vendor (CNA) |
| cbl2 kernel 5.15.179.1-1 on CBL Mariner 2.0 | 5.15.179.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.182.1-1 on CBL Mariner 2.0 | CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.182.1-1 on CBL-Mariner 2.0 | 5.15.179.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:bpftool | 7.3.0-427.37.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel | 5.14.0-427.37.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-427.37.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-427.37.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-427.37.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-427.37.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-427.37.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-427.37.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-427.37.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-427.37.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-427.37.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-427.37.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.1.128-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.1 | 6.1.128-1~deb11u1 · Debian:11 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.3.0-427.37.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-427.37.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-427.37.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-427.37.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-427.37.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-427.37.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-427.37.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+17
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).
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
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- 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:H/I:H/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 (8 more)Show less
- git.kernel.org/stable/c/2d008d4961b039d2edce8976289773961b7e5fb5
- git.kernel.org/stable/c/2dfbb920a89bdc58087672ad5325dc6c588b6860
- git.kernel.org/stable/c/95ca7c90eaf5ea8a8460536535101e3e81160e2a
- git.kernel.org/stable/c/ca710b5f40b8b16fdcad50bebd47f50e4c62d239
- git.kernel.org/stable/c/d38c49f7bdf14381270736299e2ff68ec248a017
- lists.debian.org/debian-lts-announce/2025/03/msg00001.html
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html
- cert-portal.siemens.com/productcert/html/ssa-265688.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.