LiveActive security incident?Get immediate response
CVE Record

CVE-2024-46823: kunit/overflow: Fix UB in overflow_allocation_test

In the Linux kernel, the following vulnerability has been resolved: kunit/overflow: Fix UB in overflow_allocation_test The 'device_name' array doesn't exist out of the 'overflow_allocation_test' function scope. However, it is being used as a driver name when calling 'kunit_driver_create' from 'kunit_device_register'. It produces the kernel panic with KASAN enabled. Since this variable is used in one place only, remove it and pass the device name into kunit_device_register directly as an ascii string.

HighCVSS 8.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux kernel test used a temporary name after its valid lifetime ended. When the affected KUnit overflow test runs with KASAN enabled, this can trigger a kernel panic. The supplied evidence describes a testing-path defect, not a remotely reachable production attack.

Executive priority

Prioritize promptly for kernel development, CI, and validation environments using KUnit with KASAN. For ordinary production fleets without this testing path, retain normal kernel patch urgency while confirming distribution-specific exposure; the high score alone may overstate practical reachability.

Technical view

The overflow_allocation_test passed a function-scoped device_name array through kunit_device_register for later use as a driver name, causing undefined behavior after the array's lifetime ended. KASAN exposes the defect as a kernel panic. The kernel fix passes an ASCII string directly instead.

Likely exposure

Exposure appears concentrated in systems that build or execute the affected KUnit overflow allocation test, particularly with KASAN. The bundle marks Linux version entries including 6.8, 6.10.10, and 6.11 affected, but does not clearly express complete range boundaries.

Exploitation context

The supplied CVSS vector is local, with low complexity and no required privileges or user interaction. However, no KEV listing or cited evidence supports active exploitation. The sources describe a reproducible test-time kernel panic, not a demonstrated production compromise path.

Researcher notes

The root issue is object-lifetime undefined behavior involving a function-scoped character array retained as a driver name. The supplied record reports confidentiality, integrity, and availability impacts in CVSS, but provides direct evidence only of a KASAN-observed kernel panic. No exploit chain is documented.

Mitigation direction

  • Apply an affected-distribution kernel update containing the referenced upstream fix.
  • Check vendor advisories for exact fixed package versions and supported kernel branches.
  • Avoid running the affected KUnit test on unpatched critical systems.
  • Prioritize KASAN-enabled kernel testing environments because the documented panic occurs there.

Validation and detection

  • Inventory kernel versions and compare them with vendor-specific CVE advisories.
  • Confirm whether KUnit overflow tests and KASAN are built or used.
  • Verify the deployed kernel includes either referenced stable fix commit.
  • After updating, run approved regression testing in an isolated test environment.
Prepared
Confidence
medium
Sources
5

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-46823 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
High
CVSS
8.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.4CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.55.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

8.4High
CVSS 3.1 vector shape for CVE-2024-46823Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd03c720e03bd9bf0b784d80b5d3ede7e2daf3b6e, d03c720e03bd9bf0b784d80b5d3ede7e2daf3b6eunaffected
LinuxLinux6.8, 0, 6.10.10, 6.11affected
Weakness

CWE details

No CWE listed

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