CVE-2024-43055

Memory corruption via unchecked camera IOCTL buffer copy

Published Mar 3, 2025 · Updated Mar 3, 2025

Classic buffer overflow in Camera_Linux on Qualcomm Snapdragon allows local users to corrupt memory through a camera use-case IOCTL call. Camera_Linux copies attacker-controlled IOCTL input into a destination buffer without checking that the input fits. Low-privileged local access is required; successful exploitation can expose or alter protected data and interrupt the affected execution context.

CVSS severity7.8
High
EPSS probability0.12%
Next 30 days · Sep 17, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Classic buffer overflow in Camera_Linux on Qualcomm Snapdragon allows local users to corrupt memory through a camera use-case IOCTL call. Camera_Linux copies attacker-controlled IOCTL input into a destination buffer without checking that the input fits. Low-privileged local access is required; successful exploitation can expose or alter protected data and interrupt the affected execution context.

The record

CVE
CVE-2024-43055
Published
Mar 3, 2025
Updated
Mar 3, 2025
Vendor
Qualcomm
Product
Snapdragon
Classifications
CWE-120
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Mar 3, 2025CVE publishedPublication date reported by the CVE source.
  2. Mar 3, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=FastConnect 6900
  2. Affected versionversion=FastConnect 7800
  3. Affected versionversion=SDM429W
  4. Affected versionversion=Snapdragon 429 Mobile Platform
  5. Affected versionversion=Snapdragon 8 Gen 1 Mobile Platform
  6. Affected versionversion=SXR2230P
  7. Affected versionversion=SXR2250P
  8. Affected versionversion=WCD9380
  9. Affected versionversion=WCD9385
  10. Affected versionversion=WCN3620
  11. Affected versionversion=WCN3660B
  12. Affected versionversion=WSA8830
  13. Affected versionversion=WSA8832
  14. Affected versionversion=WSA8835

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Qualcomm · Snapdragonversion=FastConnect 6900; version=FastConnect 7800; version=SDM429W; version=Snapdragon 429 Mobile Platform; version=Snapdragon 8 Gen 1 Mobile Platform; version=SXR2230P; version=SXR2250P; version=WCD9380; version=WCD9385; version=WCN3620; version=WCN3660B; version=WSA8830; version=WSA8832; version=WSA8835

Published CVSS scores

7.8Qualcomm, Inc.CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-120Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo