CVE-2023-52567

serial: 8250_port: Check IRQ data before use

MEDIUM

5.5

CVSS Score

Published: March 2, 2024 at 09:59 PM UTC

Updated: June 17, 2026 at 06:43 AM 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

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: serial: 8250_port: Check IRQ data before use In case the leaf driver wants to use IRQ polling (irq = 0) and IIR register shows that an interrupt happened in the 8250 hardware the IRQ data can be NULL. In such a case we need to skip the wake event as we came to this path from the timer interrupt and quite likely system is already awake. Without this fix we have got an Oops: serial8250: ttyS0 at I/O 0x3f8 (irq = 0, base_baud = 115200) is a 16550A ... BUG: kernel NULL pointer dereference, address: 0000000000000010 RIP: 0010:serial8250_handle_irq+0x7c/0x240 Call Trace: ? serial8250_handle_irq+0x7c/0x240 ? __pfx_serial8250_timeout+0x10/0x10

Affected

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

Linux Kernel · Linux

95%

v ≥ 6.2.15v ≥ 6.3.24.14.315 ≤ v < 4.14.3274.19.283 ≤ v < 4.19.2965.10.180 ≤ v < 5.10.1985.15.111 ≤ v < 5.15.1345.4.243 ≤ v < 5.4.2586.1.28 ≤ v < 6.1.566.2.15 ≤ v < 6.36.3.2 ≤ v < 6.46.4 ≤ v < 6.5.66.4 ≤ v < 6.60ba9e3a13c6adfa99e32b2576d20820ab10ad48a0bd49a043c7984c93c2a0af41222fb71c3986a4e4.14.315 4.19.283424cf29296354d7b9c6c038aaa7bb717821008515.10.180 5.15.111 5.4.243572d48361aa0a6e6f16c1470e5407de183493d0c6.1.28 6.2.15 6.3.2 6.6 rc1 6.6 rc2 6.6 rc3727e92fe13e81c6088a88d83e466b2b1b553c4e3d5d628fea5f6181809a9d61b04de6ade53277684d7c6aa39eb041e2a6a53106104200d11e2acc87fedfe57aedff4ecf3606533aabf8ecf7676c3c5d9f5fd2fd999b364801e9790c6f69f3fe3f40ed60f

Vendor states this is fixed in 2b837f13a818f96304736453ac53b66a70aaa4f2 (fixed)

Vendor states this is fixed in 3345cc5f02f1fb4c4dcb114706f2210d879ab933 (fixed)

Vendor states this is fixed in bf3c728e3692cc6d998874f0f27d433117348742 (fixed)

Vendor states this is fixed in c334650150c29234b0923476f51573ae1b2f252a (fixed)

Vendor states this is fixed in cce7fc8b29961b64fadb1ce398dc5ff32a79643b (fixed)

Vendor states this is fixed in e14afa4450cb7e4cf93e993a765801203d41d014 (fixed)

Vendor states this is fixed in e14f68a48fd445a083ac0750fafcb064df5f18f7 (fixed)

Vendor states this is fixed in ee5732caaffba3a37e753fdb89b4958db9a61847 (fixed)

Vendor states this is fixed in 4.14.327 (unaffected)

Vendor states this is fixed in 4.19.296 (unaffected)

Vendor states this is fixed in 5.10.198 (unaffected)

Vendor states this is fixed in 5.15.134 (unaffected)

Vendor states this is fixed in 5.4.258 (unaffected)

Vendor states this is fixed in 6.1.56 (unaffected)

Affected range stops below 6.3, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 6.4 (unaffected)

Vendor states this is fixed in 6.5.6 (unaffected)

Vendor states this is fixed in 6.6 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references