CVE-2024-36975: Linux kernel · KEYS: trusted: Do not use WARN when encode fails
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.15.0-1067.73~20.04.1 : update Linux kernel when convenient.
Data as of 12 Nov 2026, 19:04 UTC
- Patch
- Available – fixed in 5.15.0-1067.73~20.04.1, 5.15.0-1070.79~20.04.1, 5.15.0-1066.74~20.04.1 +50
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-6949-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6950-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6952-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6955-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6956-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6957-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6950-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6950-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6949-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6952-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6950-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7019-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-ibmpkg:deb/ubuntu/linux-ibm?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
In the Linux kernel, the following vulnerability has been resolved: KEYS: trusted: Do not use WARN when encode fails When asn1_encode_sequence() fails, WARN is not the correct solution. 1. asn1_encode_sequence() is not an internal function (located in lib/asn1_encode.c). 2. Location is known, which makes the stack trace useless. 3. Results a crash if panic_on_warn is set. It is also noteworthy that the use of WARN is undocumented, and it should be avoided unless there is a carefully considered rationale to use it. Replace WARN with pr_err, and print the return value instead, which is only useful piece of information.
References
- ubuntu.com/security/CVE-2024-36975 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-36975 (opens in a new tab)
- git.kernel.org/linus/050bf3c793a07f96bd1e2fd62e1447f731ed733b (opens in a new tab)
- git.kernel.org/stable/c/96f650995c70237b061b497c66755e32908f8972 (opens in a new tab)
- git.kernel.org/stable/c/681935009fec3fc22af97ee312d4a24ccf3cf087 (opens in a new tab)
- git.kernel.org/stable/c/1c652e1e10676f942149052d9329b8bf2703529a (opens in a new tab)
- git.kernel.org/stable/c/d32c6e09f7c4bec3ebc4941323f0aa6366bc1487 (opens in a new tab)
- git.kernel.org/stable/c/ff91cc12faf798f573dab2abc976c1d5b1862fea (opens in a new tab)
- git.kernel.org/stable/c/050bf3c793a07f96bd1e2fd62e1447f731ed733b (opens in a new tab)
- ubuntu.com/security/notices/USN-6949-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6950-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6952-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6955-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6956-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6957-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6950-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6950-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6949-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6952-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6950-4 (opens in a new tab)