Homepage

Deadlock The advisory has been revoked - it doesn't affect any version of package libperf  (opens in a new tab)

Threat Intelligence

EPSS
0.11% (2nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-LIBPERF-15297350
  • published17 Feb 2026
  • disclosed14 Feb 2026
Report a new vulnerability Found a mistake?

Introduced: 14 Feb 2026

CVE-2026-23168  (opens in a new tab)
CWE-833  (opens in a new tab)

Amendment

The Red Hat security team deemed this advisory irrelevant for RHEL:10.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libperf package and not the libperf package as distributed by RHEL.

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);

    &lt;hardirq is raised&gt;
    ...
    blk_mq_end_request()
  blk_update_request()
    ext4_end_bio()
      folio_end_writeback()
    __wb_writeout_add()
      __fprop_add_percpu_max()
        if (unlikely(max_frac &lt; FPROP_FRAC_BASE)) {
          fprop_fraction_percpu()
        seq = read_seqcount_begin(&amp;p-&gt;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.