Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-23168flex_proportions: make fprop_new_period() hardirq safe

Description

In the Linux kernel, the following vulnerability has been resolved: flex_proportions: make fprop_new_period() hardirq safe Bernd has reported a lockdep splat from flexible proportions code that is essentially complaining about the following race: <timer fires> run_timer_softirq - we are in softirq context call_timer_fn writeout_period fprop_new_period write_seqcount_begin(&p->sequence); <hardirq is raised> ... blk_mq_end_request() blk_update_request() ext4_end_bio() folio_end_writeback() __wb_writeout_add() __fprop_add_percpu_max() if (unlikely(max_frac < FPROP_FRAC_BASE)) { fprop_fraction_percpu() seq = read_seqcount_begin(&p->sequence); - sees odd sequence so loops indefinitely Note that a deadlock like this is only possible if the bdi has configured maximum fraction of writeout throughput which is very rare in general but frequent for example for FUSE bdis. To fix this problem we have to make sure write section of the sequence counter is irqsafe.

Timeline

  1. ID reserved

    By Linux

  2. · 32 days later

    Published

  3. · 3 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

CVSS scores of CVE-2026-23168, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.14% · top 97% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected a91befde350375b1ff954635acdde14dc92cd9a8 – < 0acc9ba7a1b5ba4d998c5753e709be904e179b75
    • affected a91befde350375b1ff954635acdde14dc92cd9a8 – < 884b2590ffcc7222cbbd6298051f4c243cc36f5d
    • affected a91befde350375b1ff954635acdde14dc92cd9a8 – < 78ede9ebd679dadf480dce6f7b798e3603f88348
    • affected a91befde350375b1ff954635acdde14dc92cd9a8 – < b91a84299d72ae0e05551e851e47cd3008bd025b
    • affected a91befde350375b1ff954635acdde14dc92cd9a8 – < dd9e2f5b38f1fdd49b1ab6d3a85f81c14369eacc
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • unaffected 6.1.162 – ≤ 6.1.*
    • unaffected 6.6.123 – ≤ 6.6.*
    • unaffected 6.12.69 – ≤ 6.12.*
    • unaffected 6.18.9 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

CVE-2026-23168 badge
[![CVE-2026-23168](https://cveledger.app/badge/CVE-2026-23168.svg)](https://cveledger.app/cve/CVE-2026-23168)

Record last updated .