CVE-2024-45012

linux: In the Linux kernel, the following vulnerability has been resolved: nouveau/firmware: use dma non-coherent allocator...

CVE-2024-45012 is fixed in 26 products on 1 platform, first by DEBIAN-CVE-2024-45012, released September 11, 2024. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
5.5
medium
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0021
10th percentile

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.

Where it's fixed

ProductFixed inFixReleased
Linux
dtb-aarch64 · opensuse-leap 15.6 6.4.0-150600.23.25.1 SUSE-SU-2024:3561-1 Oct 9, 2024
kernel-64kb · opensuse-leap 15.6 6.4.0-150600.23.25.1 SUSE-SU-2024:3561-1 Oct 9, 2024
kernel-64kb · sles 15.6 6.4.0-150600.23.25.1 SUSE-SU-2024:3561-1 Oct 9, 2024
kernel-azure · opensuse-leap 15.6 6.4.0-150600.8.14.1 SUSE-SU-2024:3551-1 Oct 8, 2024
kernel-azure · sles 15.6 6.4.0-150600.8.14.1 SUSE-SU-2024:3551-1 Oct 8, 2024
kernel-coco · sles 15.6 6.4.0-15061.6.coco15sp6.1 SUSE-SU-2024:3553-1 Oct 8, 2024
kernel-coco_debug · sles 15.6 6.4.0-15061.6.coco15sp6.1 SUSE-SU-2024:3553-1 Oct 8, 2024
kernel-debug · opensuse-leap 15.6 6.4.0-150600.23.25.1 SUSE-SU-2024:3561-1 Oct 9, 2024
kernel-default · opensuse-leap 15.6 6.4.0-150600.23.25.1 SUSE-SU-2024:3561-1 Oct 9, 2024
kernel-default · sles 15.6 6.4.0-150600.23.25.1 SUSE-SU-2024:3561-1 Oct 9, 2024
kernel-default-base · opensuse-leap 15.6 6.4.0-150600.23.25.1.150600.12.10.2 SUSE-SU-2024:3561-1 Oct 9, 2024
kernel-default-base · sles 15.6 6.4.0-150600.23.25.1.150600.12.10.2 SUSE-SU-2024:3561-1 Oct 9, 2024
kernel-docs · opensuse-leap 15.6 6.4.0-150600.23.25.2 SUSE-SU-2024:3561-1 Oct 9, 2024
kernel-docs · sles 15.6 6.4.0-150600.23.25.2 SUSE-SU-2024:3561-1 Oct 9, 2024
kernel-kvmsmall · opensuse-leap 15.6 6.4.0-150600.23.25.1 SUSE-SU-2024:3561-1 Oct 9, 2024
kernel-livepatch-SLE15-SP6-RT_Update_4 · sles 15.6 1-150600.1.3.1 SUSE-SU-2024:3564-1 Oct 9, 2024
kernel-livepatch-SLE15-SP6_Update_5 · sles 15.6 1-150600.13.3.1 SUSE-SU-2024:3561-1 Oct 9, 2024
kernel-obs-build · opensuse-leap 15.6 6.4.0-150600.23.25.2 SUSE-SU-2024:3561-1 Oct 9, 2024
kernel-obs-build · sles 15.6 6.4.0-150600.23.25.2 SUSE-SU-2024:3561-1 Oct 9, 2024
kernel-obs-qa · opensuse-leap 15.6 6.4.0-150600.23.25.1 SUSE-SU-2024:3561-1 Oct 9, 2024
kernel-rt · opensuse-leap 15.6 6.4.0-150600.10.14.1 SUSE-SU-2024:3564-1 Oct 9, 2024
kernel-rt_debug · opensuse-leap 15.6 6.4.0-150600.10.14.1 SUSE-SU-2024:3564-1 Oct 9, 2024
kernel-source · opensuse-leap 15.6 6.4.0-150600.23.25.1 SUSE-SU-2024:3561-1 Oct 9, 2024
kernel-source · sles 15.6 6.4.0-150600.23.25.1 SUSE-SU-2024:3561-1 Oct 9, 2024
kernel-source-azure · opensuse-leap 15.6 6.4.0-150600.8.14.1 SUSE-SU-2024:3551-1 Oct 8, 2024
kernel-source-azure · sles 15.6 6.4.0-150600.8.14.1 SUSE-SU-2024:3551-1 Oct 8, 2024
kernel-source-coco · sles 15.6 6.4.0-15061.6.coco15sp6.1 SUSE-SU-2024:3553-1 Oct 8, 2024
kernel-source-rt · opensuse-leap 15.6 6.4.0-150600.10.14.1 SUSE-SU-2024:3564-1 Oct 9, 2024
kernel-syms · opensuse-leap 15.6 6.4.0-150600.23.25.1 SUSE-SU-2024:3561-1 Oct 9, 2024
kernel-syms · sles 15.6 6.4.0-150600.23.25.1 SUSE-SU-2024:3561-1 Oct 9, 2024
kernel-syms-azure · opensuse-leap 15.6 6.4.0-150600.8.14.1 SUSE-SU-2024:3551-1 Oct 8, 2024
kernel-syms-azure · sles 15.6 6.4.0-150600.8.14.1 SUSE-SU-2024:3551-1 Oct 8, 2024
kernel-syms-coco · sles 15.6 6.4.0-15061.6.coco15sp6.1 SUSE-SU-2024:3553-1 Oct 8, 2024
kernel-syms-rt · opensuse-leap 15.6 6.4.0-150600.10.14.1 SUSE-SU-2024:3564-1 Oct 9, 2024
kernel-zfcpdump · opensuse-leap 15.6 6.4.0-150600.23.25.1 SUSE-SU-2024:3561-1 Oct 9, 2024
kernel-zfcpdump · sles 15.6 6.4.0-150600.23.25.1 SUSE-SU-2024:3561-1 Oct 9, 2024
linux · Debian 13.5 (trixie) 6.10.7-1 DEBIAN-CVE-2024-45012 Sep 11, 2024
linux · Debian 14 6.10.7-1 DEBIAN-CVE-2024-45012 Sep 11, 2024

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.