CVE-2023-54251

UNRATEDCVSS · not yet scored

Also known asEUVD-2023-60390 (ENISA EUVD) · GHSA-mwqv-w7x4-3822 (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net/sched: taprio: Limit TCA_TAPRIO_ATTR_SCHED_CYCLE_TIME to INT_MAX.

syzkaller found zero division error [0] in div_s64_rem() called from get_cycle_time_elapsed(), where sched->cycle_time is the divisor.

We have tests in parse_taprio_schedule() so that cycle_time will never be 0, and actually cycle_time is not 0 in get_cycle_time_elapsed().

The problem is that the types of divisor are different; cycle_time is s64, but the argument of div_s64_rem() is s32.

syzkaller fed this input and 0x100000000 is cast to s32 to be 0.

@TCA_TAPRIO_ATTR_SCHED_CYCLE_TIME={0xc, 0x8, 0x100000000}

We use s64 for cycle_time to cast it to ktime_t, so let's keep it and set max for cycle_time.

While at it, we prevent overflow in setup_txtime() and add another test in parse_taprio_schedule() to check if cycle_time overflows.

Also, we add a new tdc test case for this issue.

[0]: divide error: 0000 [#1] PREEMPT SMP KASAN NOPTI CPU: 1 PID: 103 Comm: kworker/1:3 Not tainted 6.5.0-rc1-00330-g60cc1f7d0605 #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 Workqueue: ipv6_addrconf addrconf_dad_work RIP: 0010:div_s64_rem include/linux/math64.h:42 [inline] RIP: 0010:get_cycle_time_elapsed net/sched/sch_taprio.c:223 [inline] RIP: 0010:find_entry_to_transmit+0x252/0x7e0 net/sched/sch_taprio.c:344 Code: 3c 02 00 0f 85 5e 05 00 00 48 8b 4c 24 08 4d 8b bd 40 01 00 00 48 8b 7c 24 48 48 89 c8 4c 29 f8 48 63 f7 48 99 48 89 74 24 70 <48> f7 fe 48 29 d1 48 8d 04 0f 49 89 cc 48 89 44 24 20 49 8d 85 10 RSP: 0018:ffffc90000acf260 EFLAGS: 00010206 RAX: 177450e0347560cf RBX: 0000000000000000 RCX: 177450e0347560cf RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000100000000 RBP: 0000000000000056 R08: 0000000000000000 R09: ffffed10020a0934 R10: ffff8880105049a7 R11: ffff88806cf3a520 R12: ffff888010504800 R13: ffff88800c00d800 R14: ffff8880105049a0 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff88806cf00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f0edf84f0e8 CR3: 000000000d73c002 CR4: 0000000000770ee0 PKRU: 55555554 Call Trace: get_packet_txtime net/sched/sch_taprio.c:508 [inline] taprio_enqueue_one+0x900/0xff0 net/sched/sch_taprio.c:577 taprio_enqueue+0x378/0xae0 net/sched/sch_taprio.c:658 dev_qdisc_enqueue+0x46/0x170 net/core/dev.c:3732 __dev_xmit_skb net/core/dev.c:3821 [inline] __dev_queue_xmit+0x1b2f/0x3000 net/core/dev.c:4169 dev_queue_xmit include/linux/netdevice.h:3088 [inline] neigh_resolve_output net/core/neighbour.c:1552 [inline] neigh_resolve_output+0x4a7/0x780 net/core/neighbour.c:1532 neigh_output include/net/neighbour.h:544 [inline] ip6_finish_output2+0x924/0x17d0 net/ipv6/ip6_output.c:135 __ip6_finish_output+0x620/0xaa0 net/ipv6/ip6_output.c:196 ip6_finish_output net/ipv6/ip6_output.c:207 [inline] NF_HOOK_COND include/linux/netfilter.h:292 [inline] ip6_output+0x206/0x410 net/ipv6/ip6_output.c:228 dst_output include/net/dst.h:458 [inline] NF_HOOK.constprop.0+0xea/0x260 include/linux/netfilter.h:303 ndisc_send_skb+0x872/0xe80 net/ipv6/ndisc.c:508 ndisc_send_ns+0xb5/0x130 net/ipv6/ndisc.c:666 addrconf_dad_work+0xc14/0x13f0 net/ipv6/addrconf.c:4175 process_one_work+0x92c/0x13a0 kernel/workqueue.c:2597 worker_thread+0x60f/0x1240 kernel/workqueue.c:2748 kthread+0x2fe/0x3f0 kernel/kthread.c:389 ret_from_fork+0x2c/0x50 arch/x86/entry/entry_64.S:308 Modules linked in:

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
9th
KEV
Not listed

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

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). 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
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 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 BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

December 30, 2025

Last Modified

April 15, 2026

References (4)

Vendor Advisories for CVE-2023-54251(2)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-284.88.1.el9_22024-10-16redhat
redhatkernel-0:5.14.0-427.13.1.el9_42024-04-30redhat
linuxKernel @ 5.15.126 (fixes >=5.3.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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (499 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.38-4~bpo11+1 (8 versions)
  • every version up to 6.1.52-1: fixed in 6.1.52-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.11-1: fixed in 6.4.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.11-1: fixed in 6.4.11-1
—

Data Freshness Timeline

(refreshed 7× in last 7d / 38× 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 95 of 225 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 130 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2023-54251?
CVE-2023-54251 is a vulnerability whose severity is not yet rated; its CVE record was published on December 30, 2025. In the Linux kernel, the following vulnerability has been resolved: net/sched: taprio: Limit TCA_TAPRIO_ATTR_SCHED_CYCLE_TIME to INT_MAX. syzkaller found zero division error [0] in div_s64_rem() called from get_cycle_time_elapsed(), where sched->cycle_time is the divisor. We have tests in…
When was the CVE record for CVE-2023-54251 published?
The CVE record for CVE-2023-54251 was published on December 30, 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 April 15, 2026; the record at its source may have been updated since.
Is CVE-2023-54251 actively exploited?
CVE-2023-54251 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
How do I remediate CVE-2023-54251?
A fix for CVE-2023-54251 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-54251 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-54251

Explore →

Is Your Infrastructure Affected by CVE-2023-54251?

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

Book a Demo →Browse All CVEs