Full vulnerability report · 2024

CVE-2024-45012High confidence

nouveau/firmware: use dma non-coherent allocator

Linux · Linux

5.5MediumCVSS 3.1

Recommended action

Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available

Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

14 package states

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Ubuntu release	Source package	Vendor state	Fixed version	Evidence
Ubuntu 24.04 LTSnoble · standard archive	`linux`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-aws`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gcp`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gke`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gkeop`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-ibm`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-lowlatency`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-lowlatency`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oem-6.8`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oracle`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-riscv`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current

ENISA EUVD identifier

EUVD-2024-41626

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state: Present in the current official mapping
Known exploitation: Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score: Not supplied in the stored EUVD record
Advisory evidence: No linked advisory details stored yet

Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available

What, why and how

In the Linux kernel, the following vulnerability has been resolved: nouveau/firmware: use dma non-coherent allocator Currently, enabling SG_DEBUG in the kernel will cause nouveau to hit a BUG() on startup, when the iommu is enabled: kernel BUG at include/linux/scatterlist.h:187! invalid opcode: 0000 [#1] PREEMPT SMP NOPTI CPU: 7 PID: 930 Comm: (udev-worker) Not tainted 6.9.0-rc3Lyude-Test+ #30 Hardware name: MSI MS-7A39/A320M GAMING PRO (MS-7A39), BIOS 1.I0 01/22/2019 RIP: 0010:sg_init_one+0x85/0xa0 Code: 69 88 32 01 83 e1 03 f6 c3 03 75 20 a8 01 75 1e 48 09 cb 41 89 54 24 08 49 89 1c 24 41 89 6c 24 0c 5b 5d 41 5c e9 7b b9 88 00 <0f> 0b 0f 0b 0f 0b 48 8b 05 5e 46 9a 01 eb b2 66 66 2e 0f 1f 84 00 RSP: 0018:ffffa776017bf6a0 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffffa77600d87000 RCX: 000000000000002b RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffffa77680d87000 RBP: 000000000000e000 R08: 0000000000000000 R09: 0000000000000000 R10: ffff98f4c46aa508 R11: 0000000000000000 R12: ffff98f4c46aa508 R13: ffff98f4c46aa008 R14: ffffa77600d4a000 R15: ffffa77600d4a018 FS: 00007feeb5aae980(0000) GS:ffff98f5c4dc0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f22cb9a4520 CR3: 00000001043ba000 CR4: 00000000003506f0 Call Trace: <TASK> ? die+0x36/0x90 ? do_trap+0xdd/0x100 ? sg_init_one+0x85/0xa0 ? do_error_trap+0x65/0x80 ? sg_init_one+0x85/0xa0 ? exc_invalid_op+0x50/0x70 ? sg_init_one+0x85/0xa0 ? asm_exc_invalid_op+0x1a/0x20 ? sg_init_one+0x85/0xa0 nvkm_firmware_ctor+0x14a/0x250 [nouveau] nvkm_falcon_fw_ctor+0x42/0x70 [nouveau] ga102_gsp_booter_ctor+0xb4/0x1a0 [nouveau] r535_gsp_oneinit+0xb3/0x15f0 [nouveau] ? srso_return_thunk+0x5/0x5f ? srso_return_thunk+0x5/0x5f ? nvkm_udevice_new+0x95/0x140 [nouveau] ? srso_return_thunk+0x5/0x5f ? srso_return_thunk+0x5/0x5f ? ktime_get+0x47/0xb0 Fix this by using the non-coherent allocator instead, I think there might be a better answer to this, but it involve ripping up some of APIs using sg lists.

What

Why

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Why

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: local access → Allocation of Resources Without Limits or Throttling → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Local
Privileges required: Low: a basic authenticated account is required
User interaction: None
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-770 ↗
CWE-770: Allocation of Resources Without Limits or Throttling. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land: The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.

CWE-770

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2024-41626Official EUVD mapping

0 linked advisory records.

Official EUVD record

BSI · German · WID-SEC-2024-2124Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder einen unspezifischen Angriff durchzuführen.

Official advisory

CERT-FR · French · CERTFR-2025-AVI-1057Multiples vulnérabilités dans les produits VMware

d?id=CVE-2024-44983 Référence CVE CVE-2024-44984 https://www.cve.org/CVERecord?id=CVE-2024-44984 Référence CVE CVE-2024-44986 https://www.cve.org/CVERecord?id=CVE-2024-44986 Référence CVE CVE-2024-44994 https://www.cve.org/CVERecord?id=CVE-2024-44994 Référence CVE CVE-2024-44996 https://www.cve.org/CVERecord?id=CVE-2024-44996 Référence CVE CVE-2024-45000 https://www.cve.org/CVERecord?id=CVE-2024-45000 Référence CVE CVE-2024-45001 https://www.cve.org/CVERecord?id=CVE-2024-45001 Référence CVE CVE-2024-45005 https://www.cve.org/CVERecord?id=CVE-2024-45005 Référence CVE CVE-2024-45010 https://www.cve.org/CVERecord?id=CVE-2024-45010 Référence CVE CVE-2024-45012 https://www.cve.org/CVERecord?id=CVE-2024-45012 Référence CVE CVE-2024-45013 https://www.cve.org/CVERecord?id=CVE-2024-45013 Référence CVE CVE-2024-45017 https://www.cve.org/CVERecord?id=CVE-2024-45017 Référence CVE CVE-2024-45019 https://www.cve.org/CVERecord?id=CVE-2024-45019 Référence CVE CVE-2024-45020 https://www.cve.org/CVERecord?id=CVE-2024-45020 Référence CVE CVE-2024-45022 https://www.cve.org/CVERecord?id=CVE-2024-45022 Référence CVE CVE-2024-45027 https://www.cve.org/CVERecord?id=CVE-2024-45027 Référence CVE CVE-2024-45029 https://www.cve.org/CVERecord?id=CVE-2024-45029 Référence CVE CVE-2024-45336 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2025-AVI-0022Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-45002 Référence CVE CVE-2024-45003 https://www.cve.org/CVERecord?id=CVE-2024-45003 Référence CVE CVE-2024-45005 https://www.cve.org/CVERecord?id=CVE-2024-45005 Référence CVE CVE-2024-45006 https://www.cve.org/CVERecord?id=CVE-2024-45006 Référence CVE CVE-2024-45007 https://www.cve.org/CVERecord?id=CVE-2024-45007 Référence CVE CVE-2024-45008 https://www.cve.org/CVERecord?id=CVE-2024-45008 Référence CVE CVE-2024-45009 https://www.cve.org/CVERecord?id=CVE-2024-45009 Référence CVE CVE-2024-45010 https://www.cve.org/CVERecord?id=CVE-2024-45010 Référence CVE CVE-2024-45011 https://www.cve.org/CVERecord?id=CVE-2024-45011 Référence CVE CVE-2024-45012 https://www.cve.org/CVERecord?id=CVE-2024-45012 Référence CVE CVE-2024-45013 https://www.cve.org/CVERecord?id=CVE-2024-45013 Référence CVE CVE-2024-45015 https://www.cve.org/CVERecord?id=CVE-2024-45015 Référence CVE CVE-2024-45017 https://www.cve.org/CVERecord?id=CVE-2024-45017 Référence CVE CVE-2024-45018 https://www.cve.org/CVERecord?id=CVE-2024-45018 Référence CVE CVE-2024-45019 https://www.cve.org/CVERecord?id=CVE-2024-45019 Référence CVE CVE-2024-45020 https://www.cve.org/CVERecord?id=CVE-2024-45020 Référence CVE CVE-2024-45021 https://www.cve.org/CVERecord?id=CVE-2024-45021 Référence CVE CVE-2024-45022 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2024-AVI-1080Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-45002 Référence CVE CVE-2024-45003 https://www.cve.org/CVERecord?id=CVE-2024-45003 Référence CVE CVE-2024-45005 https://www.cve.org/CVERecord?id=CVE-2024-45005 Référence CVE CVE-2024-45006 https://www.cve.org/CVERecord?id=CVE-2024-45006 Référence CVE CVE-2024-45007 https://www.cve.org/CVERecord?id=CVE-2024-45007 Référence CVE CVE-2024-45008 https://www.cve.org/CVERecord?id=CVE-2024-45008 Référence CVE CVE-2024-45009 https://www.cve.org/CVERecord?id=CVE-2024-45009 Référence CVE CVE-2024-45010 https://www.cve.org/CVERecord?id=CVE-2024-45010 Référence CVE CVE-2024-45011 https://www.cve.org/CVERecord?id=CVE-2024-45011 Référence CVE CVE-2024-45012 https://www.cve.org/CVERecord?id=CVE-2024-45012 Référence CVE CVE-2024-45013 https://www.cve.org/CVERecord?id=CVE-2024-45013 Référence CVE CVE-2024-45015 https://www.cve.org/CVERecord?id=CVE-2024-45015 Référence CVE CVE-2024-45016 https://www.cve.org/CVERecord?id=CVE-2024-45016 Référence CVE CVE-2024-45017 https://www.cve.org/CVERecord?id=CVE-2024-45017 Référence CVE CVE-2024-45018 https://www.cve.org/CVERecord?id=CVE-2024-45018 Référence CVE CVE-2024-45019 https://www.cve.org/CVERecord?id=CVE-2024-45019 Référence CVE CVE-2024-45020 https://www.cve.org/CVERecord?id=CVE-2024-45020 Référence CVE CVE-2024-45021 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2024-AVI-0870Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-45000 Référence CVE CVE-2024-45001 https://www.cve.org/CVERecord?id=CVE-2024-45001 Référence CVE CVE-2024-45002 https://www.cve.org/CVERecord?id=CVE-2024-45002 Référence CVE CVE-2024-45003 https://www.cve.org/CVERecord?id=CVE-2024-45003 Référence CVE CVE-2024-45005 https://www.cve.org/CVERecord?id=CVE-2024-45005 Référence CVE CVE-2024-45006 https://www.cve.org/CVERecord?id=CVE-2024-45006 Référence CVE CVE-2024-45007 https://www.cve.org/CVERecord?id=CVE-2024-45007 Référence CVE CVE-2024-45008 https://www.cve.org/CVERecord?id=CVE-2024-45008 Référence CVE CVE-2024-45011 https://www.cve.org/CVERecord?id=CVE-2024-45011 Référence CVE CVE-2024-45012 https://www.cve.org/CVERecord?id=CVE-2024-45012 Référence CVE CVE-2024-45013 https://www.cve.org/CVERecord?id=CVE-2024-45013 Référence CVE CVE-2024-45015 https://www.cve.org/CVERecord?id=CVE-2024-45015 Référence CVE CVE-2024-45017 https://www.cve.org/CVERecord?id=CVE-2024-45017 Référence CVE CVE-2024-45018 https://www.cve.org/CVERecord?id=CVE-2024-45018 Référence CVE CVE-2024-45019 https://www.cve.org/CVERecord?id=CVE-2024-45019 Référence CVE CVE-2024-45020 https://www.cve.org/CVERecord?id=CVE-2024-45020 Référence CVE CVE-2024-45021 https://www.cve.org/CVERecord?id=CVE-2024-45021 Référence CVE CVE-2024-45022 https://www.cve.org/CVERecord?id=

Official advisory

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Patch available
Affected: Linux: 2541626cfb794e57ba0575a6920826f591f7ced0 < cc29c5546c6a373648363ac49781f1d74b530707, 2541626cfb794e57ba0575a6920826f591f7ced0 < 57ca481fca97ca4553e8c85d6a94baf4cb40c40e, 2541626cfb794e57ba0575a6920826f591f7ced0 < 9b340aeb26d50e9a9ec99599e2a39b035fac978e, 6.2
Fixed: Linux: < 6.2, 6.6.48 ≤ 6.6.*, 6.10.7 ≤ 6.10.*, 6.11 ≤ *
Action: Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround: No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.

Evidence and provenance

Published 11 Sept 2024 · Last source change 11 May 2026, 20:33 UTC · CWE-770 · Allocation of Resources Without Limits or Throttling

CVE recordCVE.org · 5.2

CVSS sourceNIST NVD

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-08-14

European sourceENISA EUVD · EUVD-2024-41626

Product sourceCNA

Remediation sourceCVE/CNA references

CWE sourceNIST NVD

NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

2024-09-11CVE published

2026-05-11Fixed release or patch reference recorded

ENISA EUVD · EUVD-2024-41626↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

nouveau/firmware: use dma non-coherent allocator

National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

EUVD-2024-41626

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.