LiveActive security incident?Get immediate response
CVE Record

CVE-2024-46865: fou: fix initialization of grc

In the Linux kernel, the following vulnerability has been resolved: fou: fix initialization of grc The grc must be initialize first. There can be a condition where if fou is NULL, goto out will be executed and grc would be used uninitialized.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-46865 is a Linux kernel defect in the fou networking code where cleanup logic could use an uninitialized value after an error path. The public bundle confirms the issue was fixed upstream, but does not provide CVSS, impact severity, or exploit evidence.

Executive priority

Handle through normal kernel vulnerability management unless vendor guidance raises the priority. The main business risk is uncertainty: kernel defects can affect availability or isolation, but the supplied evidence does not quantify impact or exploitation.

Technical view

The kernel fix initializes grc before a branch where fou may be NULL and execution jumps to out. Without that initialization, grc could be used uninitialized in the fou path. The bundle lists upstream stable commits and downstream Debian and Siemens advisories, but no CWE or CPE detail.

Likely exposure

Exposure is limited to Linux kernels containing the vulnerable fou code path. Systems using vendor kernels, appliances, or embedded products need vendor-specific confirmation. The supplied data lists fixed Linux stable versions and commits, but no affected CPEs.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation, public exploit use, or observed attacks. Treat exploitation status as unconfirmed, not actively exploited.

Researcher notes

The useful technical signal is the uninitialized grc use on the fou NULL error path. Review the referenced stable commits for exact code context, but avoid assuming reachability, privilege requirements, or impact without vendor or upstream analysis.

Mitigation direction

  • Apply kernel updates containing the referenced Linux stable fixes.
  • Use distribution or product vendor advisories for package-specific remediation.
  • Prioritize internet-facing or tunnel-heavy Linux systems for review.
  • Check Debian LTS guidance if using affected Debian kernels.
  • Check Siemens guidance for covered Siemens products.

Validation and detection

  • Inventory Linux kernel versions across servers, devices, and appliances.
  • Compare running kernels with vendor-fixed versions and advisories.
  • Confirm whether fou-related functionality is present or enabled.
  • Verify updated systems boot into the remediated kernel.
  • Document any vendor products awaiting fixed firmware or packages.
Prepared
Confidence
medium
Sources
11

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-46865 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
3ADP providers
10Source 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

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux231c235d2f7a66f018f172e26ffd47c363f244ef, 4494bccb52ffda22ce5a1163a776d970e6229e08, d7567f098f54cb53ee3cee1c82e3d0ed9698b6b3, 1df42be305fe478ded1ee0c1d775f4ece713483b, c46cd6aaca81040deaea3500ba75126963294bd9, 7e4196935069947d8b70b09c1660b67b067e75cbunaffected
LinuxLinux5.10.226, 5.15.167, 6.1.110, 6.6.51, 6.10.10unaffected
Weakness

CWE details

No CWE listed

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