LiveActive security incident?Get immediate response
CVE Record

CVE-2024-36975: KEYS: trusted: Do not use WARN when encode fails

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can turn an error while encoding trusted-key data into a system crash on systems configured to panic on warnings. The business risk is mainly availability, not proven data theft. The source bundle provides no CVSS score and no evidence of active exploitation.

Executive priority

Treat this as a targeted availability risk for affected Linux systems, not a broadly proven compromise issue. Prioritize patching where trusted keys and panic_on_warn are present or where unexpected kernel crashes would materially affect operations.

Technical view

The trusted keys code used WARN when asn1_encode_sequence() failed. The kernel fix replaces WARN with pr_err and logs the return value because WARN can trigger a crash when panic_on_warn is enabled. The affected component is Linux kernel trusted keys; exact reachable attack conditions are not described in the provided sources.

Likely exposure

Exposure is most relevant for Linux systems using the trusted keys subsystem, especially kernels configured with panic_on_warn. The bundle lists Linux kernel affected versions and stable fix commits, but package-specific distribution status must be checked with the relevant OS vendor.

Exploitation context

CISA KEV status is false in the bundle, and no cited source states active exploitation. The described impact is a crash condition if encode failure reaches WARN on panic_on_warn systems. The sources do not establish remote exploitability, privilege requirements, or public exploit availability.

Researcher notes

The important behavior is WARN misuse in trusted-key ASN.1 encoding failure handling. The fix changes error reporting rather than introducing a complex logic change. The source bundle lacks CVSS, CWE, trigger conditions, and distribution advisories, so exposure validation should stay branch- and vendor-specific.

Mitigation direction

  • Update to a vendor kernel containing the listed stable fixes.
  • Check Linux distribution advisories for backported fixes and package names.
  • Review whether panic_on_warn is enabled on production Linux hosts.
  • Prioritize availability-sensitive systems using kernel trusted keys.
  • Avoid changing kernel panic policy without operational risk review.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Map installed kernels to vendor advisories or the listed stable commits.
  • Check whether trusted keys support is enabled or used.
  • Verify panic_on_warn configuration on exposed production systems.
  • Confirm remediation through package version or kernel build metadata.
Prepared
Confidence
medium
Sources
8

Public sources used

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-2024-36975 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
2ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf2219745250f388edacabe6cca73654131c67d0a, f2219745250f388edacabe6cca73654131c67d0a, f2219745250f388edacabe6cca73654131c67d0a, f2219745250f388edacabe6cca73654131c67d0a, f2219745250f388edacabe6cca73654131c67d0a, f2219745250f388edacabe6cca73654131c67d0aunaffected
LinuxLinux5.13, 0, 5.15.160, 6.1.92, 6.6.32, 6.8.11, 6.9.2, 6.10affected
Weakness

CWE details

No CWE listed

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