LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-23168 is a Linux kernel reliability flaw. A timing race in writeback accounting can leave kernel code looping indefinitely, creating a potential availability issue. The source says the required configuration is generally rare, but appears more often with FUSE backing devices.

Executive priority

Treat this as a targeted availability risk rather than a broad emergency. Patch through normal kernel maintenance, accelerating for FUSE-heavy systems, storage-sensitive workloads, and platforms where kernel hangs would cause material service impact.

Technical view

The flaw is in flexible proportions code. fprop_new_period() updated a sequence counter from softirq context without making the write section hardirq safe. A hardirq reader can observe an odd sequence value and spin indefinitely. The kernel stable fixes make the sequence-counter write section IRQ-safe.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel builds with writeback throughput maximum fractions configured. The source specifically calls out FUSE bdis as a frequent case. Exact distribution package impact is not provided in the bundle.

Exploitation context

The bundle does not report active exploitation, and KEV is false. The issue is described as a race-triggered deadlock condition, not a remote code execution flaw. No public exploit status is provided.

Researcher notes

The available evidence supports a kernel deadlock mechanism involving softirq timer writeout and hardirq writeback completion paths. The affected scope and severity are incomplete in the bundle, so validation should focus on vendor kernel advisories and whether relevant stable fixes are present.

Mitigation direction

  • Update to a kernel build containing the referenced stable fixes.
  • Prioritize systems using FUSE or configured writeback throughput maximum fractions.
  • Check Linux distribution advisories for backported fixes and package-specific versions.
  • Monitor kernel and vendor guidance for CVSS, affected range, and mitigation updates.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Identify hosts using FUSE-backed devices or unusual writeback throughput controls.
  • Map installed kernels to the CVE record and referenced stable commits.
  • Confirm patched kernels include the hardirq-safe fprop_new_period() change.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23168 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
6Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa91befde350375b1ff954635acdde14dc92cd9a8, a91befde350375b1ff954635acdde14dc92cd9a8, a91befde350375b1ff954635acdde14dc92cd9a8, a91befde350375b1ff954635acdde14dc92cd9a8, a91befde350375b1ff954635acdde14dc92cd9a8unaffected
LinuxLinux6.0, 0, 6.1.162, 6.6.123, 6.12.69, 6.18.9, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.