CVE-2026-68434

serial: 8250_mid: Fix NULL function pointer dereference on DNV/ICX-D/SNR platforms

N/A
Published: August 12, 2026 at 12:07 AM UTC
Updated: August 23, 2026 at 01:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: serial: 8250_mid: Fix NULL function pointer dereference on DNV/ICX-D/SNR platforms Commit b1b4efea05a5 ("serial: 8250_mid: Disable DMA for selected platforms") replaced the dnv_board setup and exit callbacks with PTR_IF(false, ...), which evaluates to NULL. However, the three call sites in mid8250_probe() and mid8250_remove() unconditionally dereference these function pointers without NULL checks, causing a NULL pointer dereference (kernel oops) on any Denverton (DNV), Ice Lake Xeon D (ICX-D/CDF), or Snowridge (SNR) platform. Fix this by adding the missing NULL checks before calling the setup and exit callbacks.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.10.261 ≤ v < 5.10.2665.15.212 ≤ v < 5.15.2176.1.178 ≤ v < 6.1.1836.12.96 ≤ v < 6.12.1016.18.39 ≤ v < 6.18.426.6.145 ≤ v < 6.6.1487.1.4 ≤ v < 7.1.60b3ed3fa227ba778cabed96e7f8d84addb8bdf9c1cd54e217c6e2cdb794a897b2f855e13ffcee5865.10.2615.15.212587afb06a5d1dc5092d3d9e9ac3ccf22094d50c66.1.1786.12.966.18.396.6.1457.1.4763d61ded752fbb3116efc951eff4363f237b7e09690e8a342632344984af72bc56b7a1fba61e6cb977855894bca4b87afa50d21e3f3e85a5a0e901fb1b4efea05a56c0995e4702a86d6624b4fdff32fc7d190bb07bf4e3b217c69370e94d1b4c80a40ad
Vendor states this is fixed in 1096397c31f6bffa95e77bdd18fbca085be83e10 (fixed)
Vendor states this is fixed in 4ea933a36a14bec19b71025cdd8407bafbd67ec1 (fixed)
Vendor states this is fixed in 600dcd548fb2b00a69f447684f52ba45d5a3540e (fixed)
Vendor states this is fixed in 7fb13fd7e9a59a37cd911efff83abe19e3ee029d (fixed)
Vendor states this is fixed in 8cbad52ccfa6a7f089cfab34979bc6cc3bff25be (fixed)
Vendor states this is fixed in b2a3eeb57ba24f8a0e34a69d40adcc63e5b9ca56 (fixed)
Vendor states this is fixed in bdaa8871b53fe9b1730ef64dda2fcd662fd83339 (fixed)
Vendor states this is fixed in f85a42fb90399dedcf81c146d09c07e4548b1e8c (fixed)
Affected range stops below 5.10.266, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.15.217, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1.183, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.12.101, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.18.42, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.6.148, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.1.6, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card