CVE-2024-43067
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMemory corruption occurs during the copying of read data from the EEPROM because the IO configuration is exposed as shared memory.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a memory corruption vulnerability in EEPROM read operations where IO configuration is incorrectly exposed as shared memory. When reading data from the EEPROM, the copying process can corrupt memory because the IO configuration (which should be protected) is accessible as shared memory, potentially allowing concurrent access or improper handling during the read operation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the Qualcomm chipset model in the deviceCheck the system hardware inventory, device firmware manifest, or kernel modules for the presence of Qca6391, Qca6426, Qca6436, Qca6574au, Qcn9074, Qcs410, or Qcs610 chipset identifiers. On Linux systems, this may appear in `lspci`, `dmesg`, or firmware dump files.Affected if The device contains any of the listed Qualcomm chipset models (Qca6391, Qca6426, Qca6436, Qca6574au, Qcn9074, Qcs410, Qcs610)
-
Confirm the firmware versionRetrieve the firmware version string from the affected Qualcomm component. This may be available via debug interfaces, firmware metadata files, or device system information. Look for firmware version strings in the EEPROM or firmware binary.Affected if Firmware version is present and matches the affected chipset models (all versions are affected)
-
Verify EEPROM access functionalityCheck if the system performs EEPROM read operations. Review any logs, diagnostics, or system calls related to EEPROM data access. This may involve examining driver behavior or network subsystem logs for EEPROM read events.Affected if The system performs EEPROM reads using the affected firmware components
If the device implements any of the affected Qualcomm chipsets (Qca6391, Qca6426, Qca6436, Qca6574au, Qcn9074, Qcs410, Qcs610) and uses EEPROM read operations, the environment is affected because all firmware versions of these products contain the memory corruption vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataFix the IO configuration handling to prevent exposure as shared memory and implement proper synchronization or memory protection mechanisms for EEPROM read operations to prevent corruption.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43067 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-43067 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data