Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2023-53783

blk-iocost: fix divide by 0 error in calc_lcoefs()

Not scoredEPSS 0.21%
Published
Updated
Reserved
Assigned by
Linux

Description

In the Linux kernel, the following vulnerability has been resolved: blk-iocost: fix divide by 0 error in calc_lcoefs() echo max of u64 to cost.model can cause divide by 0 error. # echo 8:0 rbps=18446744073709551615 > /sys/fs/cgroup/io.cost.model divide error: 0000 [#1] PREEMPT SMP RIP: 0010:calc_lcoefs+0x4c/0xc0 Call Trace: <TASK> ioc_refresh_params+0x2b3/0x4f0 ioc_cost_model_write+0x3cb/0x4c0 ? _copy_from_iter+0x6d/0x6c0 ? kernfs_fop_write_iter+0xfc/0x270 cgroup_file_write+0xa0/0x200 kernfs_fop_write_iter+0x17d/0x270 vfs_write+0x414/0x620 ksys_write+0x73/0x160 __x64_sys_write+0x1e/0x30 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x63/0xcd calc_lcoefs() uses the input value of cost.model in DIV_ROUND_UP_ULL, overflow would happen if bps plus IOC_PAGE_SIZE is greater than ULLONG_MAX, it can cause divide by 0 error. Fix the problem by setting basecost

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (7 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 7caa47151ab2e644dd221f741ec7578d9532c9a3 – < 9e8bf9f95f7a299fa9ea45b678d001806ad5e12c
    • affected 7caa47151ab2e644dd221f741ec7578d9532c9a3 – < 6e291810fe83a384700eb24a1f714966391ed562
    • affected 7caa47151ab2e644dd221f741ec7578d9532c9a3 – < 3538ade9d8c2ba41088e395de916f2599fadba8f
    • affected 7caa47151ab2e644dd221f741ec7578d9532c9a3 – < bf8eb1fd6110871e6232e8e7efe399276ef7e6f6
    • affected 7caa47151ab2e644dd221f741ec7578d9532c9a3 – < b96d7b4a9745fbd0c8384608ceb1f50415e862fa
    • affected 7caa47151ab2e644dd221f741ec7578d9532c9a3 – < 984af1e66b4126cf145153661cc24c213e2ec231
  • Linux · Linux

    • affected 5.4
    • unaffected < 5.4
    • unaffected 5.4.235 – ≤ 5.4.*
    • unaffected 5.10.173 – ≤ 5.10.*
    • unaffected 5.15.99 – ≤ 5.15.*
    • unaffected 6.1.16 – ≤ 6.1.*
    • unaffected 6.2.3 – ≤ 6.2.*
    • unaffected 6.3 – ≤ *

References (6)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-53783 badge
[![CVE-2023-53783](https://trackcve.app/badge/CVE-2023-53783.svg)](https://trackcve.app/cve/CVE-2023-53783)

Record last updated .