CVE-2023-53366

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.5 from GitHub Security Advisory published 2025-09-17. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2023-59960 (ENISA EUVD) · GHSA-rggc-f5vc-pggf (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

block: be a bit more careful in checking for NULL bdev while polling

Wei reports a crash with an application using polled IO:

PGD 14265e067 P4D 14265e067 PUD 47ec50067 PMD 0 Oops: 0000 [#1] SMP CPU: 0 PID: 21915 Comm: iocore_0 Kdump: loaded Tainted: G S 5.12.0-0_fbk12_clang_7346_g1bb6f2e7058f #1 Hardware name: Wiwynn Delta Lake MP T8/Delta Lake-Class2, BIOS Y3DLM08 04/10/2022 RIP: 0010:bio_poll+0x25/0x200 Code: 0f 1f 44 00 00 0f 1f 44 00 00 55 41 57 41 56 41 55 41 54 53 48 83 ec 28 65 48 8b 04 25 28 00 00 00 48 89 44 24 20 48 8b 47 08 <48> 8b 80 70 02 00 00 4c 8b 70 50 8b 6f 34 31 db 83 fd ff 75 25 65 RSP: 0018:ffffc90005fafdf8 EFLAGS: 00010292 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 74b43cd65dd66600 RDX: 0000000000000003 RSI: ffffc90005fafe78 RDI: ffff8884b614e140 RBP: ffff88849964df78 R08: 0000000000000000 R09: 0000000000000008 R10: 0000000000000000 R11: 0000000000000000 R12: ffff88849964df00 R13: ffffc90005fafe78 R14: ffff888137d3c378 R15: 0000000000000001 FS: 00007fd195000640(0000) GS:ffff88903f400000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000270 CR3: 0000000466121001 CR4: 00000000007706f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: iocb_bio_iopoll+0x1d/0x30 io_do_iopoll+0xac/0x250 __se_sys_io_uring_enter+0x3c5/0x5a0 ? __x64_sys_write+0x89/0xd0 do_syscall_64+0x2d/0x40 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x94f225d Code: 24 cc 00 00 00 41 8b 84 24 d0 00 00 00 c1 e0 04 83 e0 10 41 09 c2 8b 33 8b 53 04 4c 8b 43 18 4c 63 4b 0c b8 aa 01 00 00 0f 05 <85> c0 0f 88 85 00 00 00 29 03 45 84 f6 0f 84 88 00 00 00 41 f6 c7 RSP: 002b:00007fd194ffcd88 EFLAGS: 00000202 ORIG_RAX: 00000000000001aa RAX: ffffffffffffffda RBX: 00007fd194ffcdc0 RCX: 00000000094f225d RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000007 RBP: 00007fd194ffcdb0 R08: 0000000000000000 R09: 0000000000000008 R10: 0000000000000001 R11: 0000000000000202 R12: 00007fd269d68030 R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000000

which is due to bio->bi_bdev being NULL. This can happen if we have two tasks doing polled IO, and task B ends up completing IO from task A if they are sharing a poll queue. If task B completes the IO and puts the bio into our cache, then it can allocate that bio again before task A is done polling for it. As that would necessitate a preempt between the two tasks, it's enough to just be a bit more careful in checking for whether or not bio->bi_bdev is NULL.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 17, 2025

Last Modified

January 14, 2026

References (3)

Vendor Advisories for CVE-2023-53366(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 6.1.16 (fixes >=5.15.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.20-1: fixed in 6.1.20-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.20-1: fixed in 6.1.20-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.20-1: fixed in 6.1.20-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 35× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 93 of 189 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 7 repeat rows among the latest 100 are merged into the row they repeat. The 96 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:40 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  4. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  5. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  6. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-10-25 17:28 UTCEG score recompute
  10. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  11. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  12. 2026-10-24 11:35 UTCEG score recompute
  13. 2026-10-24 11:35 UTCGHSA enrichmentGHSA-rggc-f5vc-pggf · GitHub CVSS 5.5
  14. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  15. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  16. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  17. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  18. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  19. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  20. 2026-10-18 07:41 UTCEG score recompute
  21. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  22. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  23. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  24. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.2% · 8th percentile
Show 68 more
  1. 2026-10-12 18:12 UTCEG score recompute
  2. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-10-11 21:38 UTCEG score recompute
  4. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  5. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  6. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  9. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  11. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  12. 2026-10-02 05:10 UTCOSV refresh
  13. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-09-30 16:37 UTCEG score recompute
  15. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  16. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  17. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  21. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  22. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  23. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  24. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  26. 2026-09-13 00:36 UTCOSV refresh
  27. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  28. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  29. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  30. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  31. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  32. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  33. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  34. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  35. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  36. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  37. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  38. 2026-09-01 04:36 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  39. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  40. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  41. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  42. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  43. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  44. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  45. 2026-08-25 03:56 UTCOSV refresh
  46. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  47. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  48. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  49. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  50. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  51. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  52. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  53. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  54. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  55. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  56. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  57. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  58. 2026-08-08 21:19 UTCOSV refresh
  59. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  60. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  61. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  62. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  63. 2026-08-04 10:36 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  64. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  65. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  66. 2026-08-01 04:14 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  67. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  68. 2026-07-30 01:29 UTCEPSS rescoreEPSS 0.2% · 7th percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-53366?
CVE-2023-53366 is a medium-severity vulnerability; its CVE record was published on September 17, 2025. In the Linux kernel, the following vulnerability has been resolved: block: be a bit more careful in checking for NULL bdev while polling Wei reports a crash with an application using polled IO: PGD 14265e067 P4D 14265e067 PUD 47ec50067 PMD 0 Oops: 0000 [#1] SMP CPU: 0 PID: 21915 Comm: iocore_0…
When was the CVE record for CVE-2023-53366 published?
The CVE record for CVE-2023-53366 was published on September 17, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of January 14, 2026; the record at its source may have been updated since.
Is CVE-2023-53366 actively exploited?
CVE-2023-53366 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53366?
CVE-2023-53366 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-53366?
A fix for CVE-2023-53366 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-53366 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-53366

Explore →

Is Your Infrastructure Affected by CVE-2023-53366?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs