CVE-2026-43368·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: drm/i915: Fix potential overflow of shmem scatterlist length When a scatterlists table of a GEM shmem object of size 4 GB or more is populated with pages allocated from a folio, unsigned int .length attribute of a scatterlist may get overflowed if total byte length of pages allocated to that single scatterlist happens to reach or cross the 4GB limit. As a consequence, users of the object may suffer from hitting unexpected, premature end of the object's backing pages. [278.780187] ------------[ cut here ]------------ [278.780377] WARNING: CPU: 1 PID: 2326 at drivers/gpu/drm/i915/i915_mm.c:55 remap_sg+0x199/0x1d0 [i915] ... [278.780654] CPU: 1 UID: 0 PID: 2326 Comm: gem_mmap_offset Tainted: G S U 6.17.0-rc1-CI_DRM_16981-ged823aaa0607+ #1 PREEMPT(voluntary) [278.780656] Tainted: [S]=CPU_OUT_OF_SPEC, [U]=USER [278.780658] Hardware name: Intel Corporation Meteor Lake Client Platform/MTL-P LP5x T3 RVP, BIOS MTLPFWI1.R00.3471.D91.2401310918 01/31/2024 [278.780659] RIP: 0010:remap_sg+0x199/0x1d0 [i915] ... [278.780786] Call Trace: [278.780787] <TASK> [278.780788] ? __apply_to_page_range+0x3e6/0x910 [278.780795] ? __pfx_remap_sg+0x10/0x10 [i915] [278.780906] apply_to_page_range+0x14/0x30 [278.780908] remap_io_sg+0x14d/0x260 [i915] [278.781013] vm_fault_cpu+0xd2/0x330 [i915] [278.781137] __do_fault+0x3a/0x1b0 [278.781140] do_fault+0x322/0x640 [278.781143] __handle_mm_fault+0x938/0xfd0 [278.781150] handle_mm_fault+0x12c/0x300 [278.781152] ? lock_mm_and_find_vma+0x4b/0x760 [278.781155] do_user_addr_fault+0x2d6/0x8e0 [278.781160] exc_page_fault+0x96/0x2c0 [278.781165] asm_exc_page_fault+0x27/0x30 ... That issue was apprehended by the author of a change that introduced it, and potential risk even annotated with a comment, but then never addressed. When adding folio pages to a scatterlist table, take care of byte length of any single scatterlist not exceeding max_segment. (cherry picked from commit 06249b4e691a75694c014a61708c007fb5755f60)
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.19.9
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.13% — higher than 2% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-43368 scores 7.8 on CVSS, so a successful attack would be serious — but at 0.13%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.19
Until: 6.19.9
Fixed in: 6.19.9
How to fix this CVE
Update your Linux kernel to version 6.19.9 or later to patch the scatterlist overflow vulnerability affecting the i915 GPU driver. This fix ensures that memory page allocations for large GEM shmem objects (4GB+) are properly segmented to prevent integer overflow in scatterlist length fields. Apply the kernel update through your distribution's package manager and reboot your system to activate the patch.
sudo dnf update kernelDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your current kernel version with `uname -r` and verify if it falls in the 6.19.0-6.19.8 range
- Step 2: Verify i915 GPU driver is loaded by running `lsmod | grep i915` (affects Intel integrated/discrete GPUs)
- Step 3: Search kernel logs for scatterlist-related warnings with `sudo dmesg | grep -i 'scatterlist\|remap_sg\|overflow'`
- Step 4: After updating, confirm the new kernel version with `uname -r` and verify it shows 6.19.9 or later
FAQ
What is CVE-2026-43368?
This vulnerability affects the i915 Intel GPU driver's handling of very large (4GB+) GPU memory objects, where an unsigned integer overflow in scatterlist page length tracking can cause premature termination of memory access, leading to system instability or denial of service.
Is CVE-2026-43368 being actively exploited?
No, this vulnerability is not currently listed on CISA's Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available, though the risk has been documented by kernel developers.
What versions of Kernel are affected by CVE-2026-43368?
Linux kernel versions 6.19.0 through 6.19.8 are affected. The vulnerability was fixed in kernel 6.19.9 and later versions.
How do I check if my server is vulnerable to CVE-2026-43368?
Run `uname -r` to display your kernel version. If it shows 6.19.0 through 6.19.8 and `lsmod | grep i915` returns output, your system is vulnerable. Run `sudo dmesg | tail -100` to check for any existing scatterlist-related kernel warnings.
Does Defensia detect CVE-2026-43368?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2026-43368 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/029ae067431ab9d0fca479bdabe780fa436706ea
- https://git.kernel.org/stable/c/1c956f0fccc26fefcbb507516c49d1db41c40471
- https://git.kernel.org/stable/c/21a301f12d18797bf889c15497f922edfdaece3a
- https://git.kernel.org/stable/c/aeb7255531ba4a5c3a64938577170d08b78de399
- https://git.kernel.org/stable/c/eae4bf4107571283031db96ce132e951615e2ae4
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-43368. Free for 1 server.
Get started free