← console
voxell vciy

CVE-2021-47387: cpufreq: schedutil: Use kobject release() method to free sugov_tunables

ROUTINE

Telemetry drift only. No threshold crossed and no authority ruling changed.

CVE record, CISA KEV and EPSS as of 2026-10-18.

CVEs like this one computed, by meaning

What to do now held facts and links

  1. Upgrade to the fixed version for your release line, or later: kernel 4.14.249; kernel 4.19.209; kernel 4.9.285; kernel 5.10.71; kernel 5.14.10; kernel 5.4.151 upper bounds of the CVE record's affected ranges
  2. Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
  3. Check your version against the ranges this record publishes.

What it is stated by the CNA

In the Linux kernel, the following vulnerability has been resolved: cpufreq: schedutil: Use kobject release() method to free sugov_tunables The struct sugov_tunables is protected by the kobject, so we can't free it directly. Otherwise we would get a call trace like this: ODEBUG: free active (active state 0) object type: timer_list hint: delayed_work_timer_fn+0x0/0x30 WARNING: CPU: 3 PID: 720 at lib/debugobjects.c:505 debug_print_object+0xb8/0x100 Modules linked in: CPU: 3 PID: 720 Comm: a.sh Tainted: G W 5.14.0-rc1-next-20210715-yocto-standard+ #507 Hardware name: Marvell OcteonTX CN96XX board (DT) pstate: 40400009 (nZcv daif +PAN -UAO -TCO BTYPE=--) pc : debug_print_object+0xb8/0x100 lr : debug_print_object+0xb8/0x100 sp : ffff80001ecaf910 x29: ffff80001ecaf910 x28: ffff00011b10b8d0 x27: ffff800011043d80 x26: ffff00011a8f0000 x25: ffff800013cb3ff0…

weakness
Not named by the CNA. NVD maps it to CWE-763.
affected
Linux
published ranges
linux kernel >= 4.7 < 4.9.285; linux kernel >= 4.10 < 4.14.249; linux kernel >= 4.15 < 4.19.209; linux kernel >= 4.20 < 5.4.151; and 2 more on the CVE page
first unaffected version, by branch
kernel 4.14.249; kernel 4.19.209; kernel 4.9.285; kernel 5.10.71; kernel 5.14.10; kernel 5.4.151
assigned by
Linux
published
2024-05-21

check us git.kernel.org git.kernel.org git.kernel.org git.kernel.org

Exploit code held, dated

exploit code
None held in the PoC-in-GitHub feed. A public repository changes this brief.

What moved held, dated

dateEPSSevent
22 May 20240.00044
17 Mar 20250.00094scoring model v2025.03.14
29 Mar 20250.00396
30 Mar 20250.00094
30 Apr 20250.00072
2 May 20250.00094
15 May 20250.00072
16 May 20250.00094
29 Jun 20250.00133
30 Jun 20250.0009
22 Jul 20250.00019
23 Jul 20250.00018
26 Sep 20250.00007
18 Nov 20250.00068
21 Nov 20250.00007
15 Jun 20260.00251scoring model v2026.06.15

16 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.

Outside the record researched, cited

This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.

Sign in to add the researched section

What would change this brief held, dated

CISA KEV
Not listed in the catalogue we hold. A listing changes this brief.
exploit probability
0.00 on 2026-06-15 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
fix
Held: kernel 4.14.249; kernel 4.19.209; kernel 4.9.285; kernel 5.10.71; kernel 5.14.10; kernel 5.4.151. A newer fix from the CNA or OSV changes this brief.

Watch this CVE What counts as a move

How to check this

Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:

SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2021-47387', '2026-11-01T23:59:59.999999Z', now());