Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-26984: nouveau: fix instmem race condition around ptr stores

MediumCVSS 5.5 · v3.1—No exploit Fix available

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.20% (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 13d76b2f443dc371842916dd8768009ff1594716, 1bc4825d4c3ec6abe43cf06c3c39d664d044cbf7, 21ca9539f09360fd83654f78f2c361f2f5ddcb52; azl3 hyperv-daemons 6.6.22.1-2 on Azure Linux 3.0 6.6.35.1-1; azl3 hyperv-daemons 6.6.35.1-1 on Azure Linux 3.0 6.6.35.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 13d76b2f443dc371842916dd8768009ff1594716, 1bc4825d4c3ec6abe43cf06c3c39d664d044cbf7, 21ca9539f09360fd83654f78f2c361f2f5ddcb52; azl3 hyperv-daemons 6.6.22.1-2 on Azure Linux 3.0 6.6.35.1-1; azl3 hyperv-daemons 6.6.35.1-1 on Azure Linux 3.0 6.6.35.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: nouveau: fix instmem race condition around ptr stores Running a lot of VK CTS in parallel against nouveau, once every few hours you might see something like this crash. BUG: kernel NULL pointer dereference, address: 0000000000000008 PGD 8000000114e6e067 P4D 8000000114e6e067 PUD 109046067 PMD 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 7 PID: 53891 Comm: deqp-vk Not tainted 6.8.0-rc6+ #27 Hardware name: Gigabyte Technology Co., Ltd. Z390 I AORUS PRO WIFI/Z390 I AORUS PRO WIFI-CF, BIOS F8 11/05/2021 RIP: 0010:gp100_vmm_pgt_mem+0xe3/0x180 [nouveau] Code: c7 48 01 c8 49 89 45 58 85 d2 0f 84 95 00 00 00 41 0f b7 46 12 49 8b 7e 08 89 da 42 8d 2c f8 48 8b 47 08 41 83 c7 01 48 89 ee <48> 8b 40 08 ff d0 0f 1f 00 49 8b 7e 08 48 89 d9 48 8d 75 04 48 c1 RSP: 0000:ffffac20c5857838 EFLAGS: 00010202 RAX: 0000000000000000 RBX: 00000000004d8001 RCX: 0000000000000001 RDX: 00000000004d8001 RSI: 00000000000006d8 RDI: ffffa07afe332180 RBP: 00000000000006d8 R08: ffffac20c5857ad0 R09: 0000000000ffff10 R10: 0000000000000001 R11: ffffa07af27e2de0 R12: 000000000000001c R13: ffffac20c5857ad0 R14: ffffa07a96fe9040 R15: 000000000000001c FS: 00007fe395eed7c0(0000) GS:ffffa07e2c980000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000008 CR3: 000000011febe001 CR4: 00000000003706f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: ... ? gp100_vmm_pgt_mem+0xe3/0x180 [nouveau] ? gp100_vmm_pgt_mem+0x37/0x180 [nouveau] nvkm_vmm_iter+0x351/0xa20 [nouveau] ? __pfx_nvkm_vmm_ref_ptes+0x10/0x10 [nouveau] ? __pfx_gp100_vmm_pgt_mem+0x10/0x10 [nouveau] ? __pfx_gp100_vmm_pgt_mem+0x10/0x10 [nouveau] ? __lock_acquire+0x3ed/0x2170 ? __pfx_gp100_vmm_pgt_mem+0x10/0x10 [nouveau] nvkm_vmm_ptes_get_map+0xc2/0x100 [nouveau] ? __pfx_nvkm_vmm_ref_ptes+0x10/0x10 [nouveau] ? __pfx_gp100_vmm_pgt_mem+0x10/0x10 [nouveau] nvkm_vmm_map_locked+0x224/0x3a0 [nouveau] Adding any sort of useful debug usually makes it go away, so I hand wrote the function in a line, and debugged the asm. Every so often pt->memory->ptrs is NULL. This ptrs ptr is set in the nv50_instobj_acquire called from nvkm_kmap. If Thread A and Thread B both get to nv50_instobj_acquire around the same time, and Thread A hits the refcount_set line, and in lockstep thread B succeeds at refcount_inc_not_zero, there is a chance the ptrs value won't have been stored since refcount_set is unordered. Force a memory barrier here, I picked smp_mb, since we want it on all CPUs and it's write followed by a read. v2: use paired smp_rmb/smp_wmb.

Published
May 1, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 10th percentile

Report tools

JSON

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.

Follow CVE-2024-26984

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

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 help

Affected 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.

VendorProduct
linuxlinux kernel
debiandebian linux

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

    • 4.15affected
    • be55287aa5ba6895e9d4d3ed2f08a1be7a065957 and later · before bba8ec5e9b16649d85bc9e9086bf7ae5b5716ff9affected · git
    • be55287aa5ba6895e9d4d3ed2f08a1be7a065957 and later · before 1bc4825d4c3ec6abe43cf06c3c39d664d044cbf7affected · git
    • be55287aa5ba6895e9d4d3ed2f08a1be7a065957 and later · before 13d76b2f443dc371842916dd8768009ff1594716affected · git
    • be55287aa5ba6895e9d4d3ed2f08a1be7a065957 and later · before 3ab056814cd8ab84744c9a19ef51360b2271c572affected · git
    • be55287aa5ba6895e9d4d3ed2f08a1be7a065957 and later · before ad74d208f213c06d860916ad40f609ade8c13039affected · git
    • be55287aa5ba6895e9d4d3ed2f08a1be7a065957 and later · before a019b44b1bc6ed224c46fb5f88a8a10dd116e525affected · git
    • be55287aa5ba6895e9d4d3ed2f08a1be7a065957 and later · before 21ca9539f09360fd83654f78f2c361f2f5ddcb52affected · git
    • be55287aa5ba6895e9d4d3ed2f08a1be7a065957 and later · before fff1386cc889d8fb4089d285f883f8cba62d82ceaffected · git
    • before 4.15not affected · semver
Affected versions · NVD (9)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux10.0
  • linux linux kernel4.20 and later · before 5.4.275
  • linux linux kernel5.5 and later · before 5.10.216
  • linux linux kernel5.11 and later · before 5.15.157
  • linux linux kernel4.15 and later · before 4.19.313
  • linux linux kernel6.2 and later · before 6.6.29
  • linux linux kernel6.7 and later · before 6.8.8
  • linux linux kernel5.16 and later · before 6.1.88
  • linux linux kernel6.9

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.117.1.el8_104.18.0-553.117.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.117.1.el8_104.18.0-553.117.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.117.1.el8_104.18.0-553.117.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.117.1.el8_104.18.0-553.117.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.117.1.el8_104.18.0-553.117.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.117.1.el8_104.18.0-553.117.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.117.1.el8_104.18.0-553.117.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.117.1.el8_104.18.0-553.117.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.117.1.el8_104.18.0-553.117.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.117.1.el8_104.18.0-553.117.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.117.1.el8_104.18.0-553.117.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.117.1.el8_104.18.0-553.117.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.117.1.el8_104.18.0-553.117.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.117.1.el8_104.18.0-553.117.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.117.1.el8_104.18.0-553.117.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.117.1.rt7.458.el8_104.18.0-553.117.1.rt7.458.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.117.1.rt7.458.el8_104.18.0-553.117.1.rt7.458.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.117.1.rt7.458.el8_104.18.0-553.117.1.rt7.458.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.117.1.rt7.458.el8_104.18.0-553.117.1.rt7.458.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.117.1.rt7.458.el8_104.18.0-553.117.1.rt7.458.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.117.1.rt7.458.el8_104.18.0-553.117.1.rt7.458.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.117.1.rt7.458.el8_104.18.0-553.117.1.rt7.458.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.117.1.rt7.458.el8_104.18.0-553.117.1.rt7.458.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.117.1.rt7.458.el8_104.18.0-553.117.1.rt7.458.el8_10

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-26981May 1, 2024 · nilfs2: fix OOB in nilfs_set_de_type
    31Monitor
  • ← EarlierCVE-2024-26983May 1, 2024 · bootconfig: use memblock_free_late to free xbc memory to buddy
    31Monitor
  • Later →CVE-2024-26985May 1, 2024 · drm/xe: Fix bo leak in intel_fb_bo_framebuffer_init
    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 / packageFixed versionSource
Linux Linux13d76b2f443dc371842916dd8768009ff1594716Vendor (CNA)
Linux Linux1bc4825d4c3ec6abe43cf06c3c39d664d044cbf7Vendor (CNA)
Linux Linux21ca9539f09360fd83654f78f2c361f2f5ddcb52Vendor (CNA)
Linux Linux3ab056814cd8ab84744c9a19ef51360b2271c572Vendor (CNA)
Linux Linuxa019b44b1bc6ed224c46fb5f88a8a10dd116e525Vendor (CNA)
Linux Linuxad74d208f213c06d860916ad40f609ade8c13039Vendor (CNA)
Linux Linuxbba8ec5e9b16649d85bc9e9086bf7ae5b5716ff9Vendor (CNA)
Linux Linuxfff1386cc889d8fb4089d285f883f8cba62d82ceVendor (CNA)
azl3 hyperv-daemons 6.6.22.1-2 on Azure Linux 3.06.6.35.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 hyperv-daemons 6.6.35.1-1 on Azure Linux 3.06.6.35.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 hyperv-daemons 5.15.153.1-1 on CBL Mariner 2.05.15.158.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 hyperv-daemons 5.15.158.1-1 on CBL Mariner 2.05.15.158.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool4.18.0-553.117.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.117.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.117.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.117.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.117.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.117.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.117.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.117.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.117.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.117.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.117.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.117.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.90-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.0.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)

+9

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.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

References

Show all references (12 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records