LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49946: clk: bcm: rpi: Prevent out-of-bounds access

In the Linux kernel, the following vulnerability has been resolved: clk: bcm: rpi: Prevent out-of-bounds access The while loop in raspberrypi_discover_clocks() relies on the assumption that the id of the last clock element is zero. Because this data comes from the Videocore firmware and it doesn't guarantuee such a behavior this could lead to out-of-bounds access. So fix this by providing a sentinel element.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects Raspberry Pi BCM clock discovery. The kernel trusted clock data from VideoCore firmware to end with a zero identifier; if it did not, the loop could read past valid data. The public record does not provide impact, CVSS, or confirmed exploitation.

Executive priority

Treat as a kernel maintenance item with unknown severity. Prioritize fleets running Raspberry Pi or related BCM platforms, but do not assume active exploitation from the provided evidence.

Technical view

In raspberrypi_discover_clocks(), a while loop assumed the last firmware-provided clock entry had id zero. The fix adds an explicit sentinel element to prevent out-of-bounds access when VideoCore firmware does not provide that terminator.

Likely exposure

Exposure is most likely on affected Linux kernels using the Raspberry Pi BCM clock driver path with VideoCore firmware-provided clock data. The source bundle lists Linux as affected across kernel version ranges, but does not provide CPEs or distro package mappings.

Exploitation context

The bundle reports no CISA KEV listing and provides no cited evidence of active exploitation or public exploit details. Exploitability is unclear because the public record does not define attacker control, required privileges, or practical impact.

Researcher notes

Key uncertainty is exploitability. The root cause is source-grounded, but the bundle lacks CVSS, CWE, attack vector, privilege requirements, and distro-specific fixed versions. Avoid extrapolating beyond the kernel clock driver context.

Mitigation direction

  • Update affected Linux kernels using vendor or distribution guidance.
  • Prioritize Raspberry Pi or Broadcom BCM Linux deployments for review.
  • Confirm deployed kernels include one of the referenced stable fixes.
  • Track CVE Program and kernel stable updates for severity changes.

Validation and detection

  • Inventory Linux kernel versions across relevant devices.
  • Identify systems using the Raspberry Pi BCM clock driver path.
  • Compare kernel source or package changelog against referenced stable commits.
  • Verify vendor advisories for fixed package versions.
  • Document any systems that cannot be promptly updated.
Prepared
Confidence
medium
Sources
6

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-2022-49946 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
0ADP providers
5Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux93d2725affd65686792f4b57e49ef660f3c8c0f9, 93d2725affd65686792f4b57e49ef660f3c8c0f9, 93d2725affd65686792f4b57e49ef660f3c8c0f9, 93d2725affd65686792f4b57e49ef660f3c8c0f9unaffected
LinuxLinux5.9, 0, 5.10.142, 5.15.66, 5.19.8, 6.0affected
Weakness

CWE details

No CWE listed

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