dbcve.org
Aqt1000 FirmwareOperating system · Qualcomm

CVE-2023-28583

HIGH · 7.8 CVSS v3.1 Published 2024-01-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Memory corruption when IPv6 prefix timer object`s lifetime expires which are created while Netmgr daemon gets an IPv6 address.

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 confidence

Memory corruption occurs in the Netmgr daemon when IPv6 prefix timer objects, created during IPv6 address configuration, have their lifetime expire. The vulnerability stems from improper lifecycle management of these timer objects, likely a use-after-free condition where timer callback execution occurs after the associated memory has been freed.

MitigationApply the vendor security patch for this vulnerability. If no patch is available, consider upgrading to a patched version of the affected software or temporarily disabling IPv6 functionality as a workaround.

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 data
Aqt1000 FirmwareOperating system
Affected:all versions
Fastconnect 6200 FirmwareOperating system
Affected:all versions
Qca6420 FirmwareOperating system
Affected:all versions
Qca6430 FirmwareOperating system
Affected:all versions
Qca6574au FirmwareOperating system
Affected:all versions
Qca6696 FirmwareOperating system
Affected:all versions
Sa6145p FirmwareOperating system
Affected:all versions
Sa6150p FirmwareOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Qualcomm chipset and firmware version
    Examine the system firmware or boot logs to determine the exact chipset model (Aqt1000, Fastconnect 6200, Qca6420, Qca6430, Qca6574au, Qca6696, Sa6145p, or Sa6150p) and firmware version. This information is typically found in /proc/cpuinfo, boot messages, or device-specific diagnostic interfaces.
    Affected if The device runs any of the listed affected chipsets (Aqt1000, Fastconnect 6200, Qca6420, Qca6430, Qca6574au, Qca6696, Sa6145p, Sa6150p) with any firmware version.
  2. Verify IPv6 is enabled
    Check the system network configuration for IPv6 support. On Linux systems, inspect /proc/sys/net/ipv6/conf/all/disable_ipv6 or use 'ip -6 addr show'. On embedded systems, examine the network configuration files or runtime settings.
    Affected if IPv6 is enabled and the system is configured to assign IPv6 addresses, which creates the prefix timer objects that trigger the vulnerability.
  3. Confirm Netmgr daemon is running
    Check for the presence and status of the Netmgr (network manager) daemon process. Use commands such as 'ps', 'systemctl status netmgr', or examine process lists specific to the embedded platform.
    Affected if The Netmgr daemon is active and managing network interfaces, particularly IPv6 configuration.
  4. Check for Netmgr-related crash logs or memory corruption
    Review system logs (/var/log/messages, dmesg, or platform-specific log locations) for any Netmgr daemon crashes, memory corruption reports, or use-after-free errors, especially those mentioning IPv6 prefix or timer objects.
    Affected if Logs show Netmgr crashes or memory corruption errors related to IPv6 prefix timer handling.

A device is affected if it uses any of the listed Qualcomm chipsets (Aqt1000, Fastconnect 6200, Qca6420, Qca6430, Qca6574au, Qca6696, Sa6145p, Sa6150p) with IPv6 functionality enabled and the Netmgr daemon active.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor security patch for this vulnerability. If no patch is available, consider upgrading to a patched version of the affected software or temporarily disabling IPv6 functionality as a workaround.

Fix this in Aqt1000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28583 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-28583 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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