Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-50096: nouveau/dmem: Fix vulnerability in migrate_to_ram upon copy error

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.24% (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 614bfb2050982d23d53d0d51c4079dba0437c883, 697e3ddcf1f8b68bd531fc34eead27c000bdf3e1, 73f75d2b5aee5a735cf64b8ab4543d5c20dbbdd9; cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.0 5.15.173.1-1; cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.0 5.15.173.1-1.

Low priority for now. Upgrade to Linux Linux 614bfb2050982d23d53d0d51c4079dba0437c883, 697e3ddcf1f8b68bd531fc34eead27c000bdf3e1, 73f75d2b5aee5a735cf64b8ab4543d5c20dbbdd9; cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.0 5.15.173.1-1; cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.0 5.15.173.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/dmem: Fix vulnerability in migrate_to_ram upon copy error The `nouveau_dmem_copy_one` function ensures that the copy push command is sent to the device firmware but does not track whether it was executed successfully. In the case of a copy error (e.g., firmware or hardware failure), the copy push command will be sent via the firmware channel, and `nouveau_dmem_copy_one` will likely report success, leading to the `migrate_to_ram` function returning a dirty HIGH_USER page to the user. This can result in a security vulnerability, as a HIGH_USER page that may contain sensitive or corrupted data could be returned to the user. To prevent this vulnerability, we allocate a zero page. Thus, in case of an error, a non-dirty (zero) page will be returned to the user.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Nov 5, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 15th percentile
CWE
—

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.

CNA vs NVD score

NVD
5.5
CNA · Linux
7.3
1.8 point gap

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

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.

Follow CVE-2024-50096

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

Your free account also gets you

  • Stack 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 (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.

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

Affected versions

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

  • linux linux kernel5.1 and later · before 5.4.285
  • linux linux kernel5.5 and later · before 5.10.227
  • linux linux kernel5.11 and later · before 5.15.168
  • linux linux kernel5.16 and later · before 6.1.113
  • linux linux kernel6.2 and later · before 6.6.57
  • linux linux kernel6.7 and later · before 6.11.4
  • linux linux kernel6.12

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.1affected
    • 5be73b690875f7eb2d2defb54ccd7f2f12074984 and later · before fd9bb7e996bab9b9049fffe3f3d3b50dee191d27affected · git
    • 5be73b690875f7eb2d2defb54ccd7f2f12074984 and later · before 73f75d2b5aee5a735cf64b8ab4543d5c20dbbdd9affected · git
    • 5be73b690875f7eb2d2defb54ccd7f2f12074984 and later · before 8c3de9282dde21ce3c1bf1bde3166a4510547aa9affected · git
    • 5be73b690875f7eb2d2defb54ccd7f2f12074984 and later · before 614bfb2050982d23d53d0d51c4079dba0437c883affected · git
    • 5be73b690875f7eb2d2defb54ccd7f2f12074984 and later · before 697e3ddcf1f8b68bd531fc34eead27c000bdf3e1affected · git
    • 5be73b690875f7eb2d2defb54ccd7f2f12074984 and later · before ab4d113b6718b076046018292f821d5aa4b844f8affected · git
    • 5be73b690875f7eb2d2defb54ccd7f2f12074984 and later · before 835745a377a4519decd1a36d6b926e369b3033e2affected · git
    • before 5.1not affected · semver
    • 5.4.285 and later · up to and including 5.4.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.115-16.1.115-1
Debian:13linuxbefore 6.11.4-16.11.4-1

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-50093Nov 5, 2024 · thermal: intel: int340x: processor: Fix warning during module unload
    22Monitor
  • ← EarlierCVE-2024-50094Nov 5, 2024 · sfc: Don't invoke xdp_do_flush() from netpoll.
    22Monitor
  • Later →CVE-2024-50097Nov 5, 2024 · net: fec: don't save PTP state if PTP is unsupported
    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 Linux614bfb2050982d23d53d0d51c4079dba0437c883Vendor (CNA)
Linux Linux697e3ddcf1f8b68bd531fc34eead27c000bdf3e1Vendor (CNA)
Linux Linux73f75d2b5aee5a735cf64b8ab4543d5c20dbbdd9Vendor (CNA)
Linux Linux835745a377a4519decd1a36d6b926e369b3033e2Vendor (CNA)
Linux Linux8c3de9282dde21ce3c1bf1bde3166a4510547aa9Vendor (CNA)
Linux Linuxab4d113b6718b076046018292f821d5aa4b844f8Vendor (CNA)
Linux Linuxfd9bb7e996bab9b9049fffe3f3d3b50dee191d27Vendor (CNA)
cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.173.1-1 on CBL Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.115-1 · Debian:12Package 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.

Finders, 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
none
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

—

CVSS vector

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

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.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records