Vulnerability · CVE-2023-54251
In the Linux kernel, the following vulnerability has been resolved: net/sched: taprio: Limit TCA_TAPRIO_ATTR_SCHED_CYCLE_TIME to INT_MAX.
Published Dec 30, 2025 · catalog updated May 11, 2026 · Linux Linux
Last checked Nov 1, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2023-54251. EPSS is 0.20%. Act only if a listed version of Linux Linux is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-99164 · High
- CVE-2026-99158 · Unknown
- CVE-2026-99157 · Unknown
- CVE-2026-99154 · Critical
- CVE-2026-99123 · High
- Severity
- None0.0
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.20%
- Remediation
- Version ranges on file
- Affected products
- vendor Linux Linux 4cfd5779bd6efe8c76b4494aec63a063be0d2ff2 <0b45af982a4df0b14fb8669ee2a871cfdfa6a39c
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_T
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor Linux Linux 4cfd5779bd6efe8c76b4494aec63a063be0d2ff2 <0b45af982a4df0b14fb8669ee2a871cfdfa6a39c4cfd5779bd6efe8c76b4494aec63a063be0d2ff2 <0b45af982a4df0b14fb8669ee2a871cfdfa6a39c
How to fix CVE-2023-54251
Upgrade
CVE-2023-54251 lists a fix boundary at 0b45af982a4df0b14fb8669ee2a871cfdfa6a39c. Compare the installed build with that boundary before you change production.
Version check
Seen in 4cfd5779bd6efe8c76b4494aec63a063be0d2ff2 <0b45af982a4df0b14fb8669ee2a871cfdfa6a39c
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2023-54251. EPSS is 0.20%. Act only if a listed version of Linux Linux is installed.
Which versions are affected?
Compare what you have installed with Linux Linux 4cfd5779bd6efe8c76b4494aec63a063be0d2ff2 <0b45af982a4df0b14fb8669ee2a871cfdfa6a39c 4cfd5779bd6efe8c76b4494aec63a063be0d2ff2 <0b45af982a4df0b14fb8669ee2a871cfdfa6a39c. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.20%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Dec 30, 2025 · EUVD
Detected
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
May 11, 2026 · EUVD
Updated
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
Sources
- CVE.orgVulnerability recordCVE-2023-54251
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2023-54251
30-day exploitation probability 0.20%
first.org - EUVDVulnerability recordEUVD-2023-60390
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
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Nov 1, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSNov 1, 2026
- CVE.orgOct 29, 2026
- EUVDOct 29, 2026