CVE-2022-21742
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 · uneditedRealtek USB driver has a buffer overflow vulnerability due to insufficient parameter length verification in the API function. An unauthenticated LAN attacker can exploit this vulnerability to disrupt services.
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 confidenceRealtek USB driver contains a buffer overflow vulnerability due to insufficient parameter length validation in an API function. An unauthenticated attacker on the local network can exploit this to disrupt services via the overflow.
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>= 7.42, <= 7.53>= 8.49, <= 8.60>= 10.28, < 10.50>= 7.42, <= 7.53>= 8.49, <= 8.60>= 10.28, < 10.50>= 7.42, <= 7.53>= 8.49, <= 8.60>= 10.28, < 10.50>= 7.42, <= 7.53>= 8.49, <= 8.60>= 10.28, < 10.50>= 7.42, <= 7.53>= 8.49, <= 8.60>= 10.28, < 10.50>= 7.42, <= 7.53>= 8.49, <= 8.60>= 10.28, < 10.50>= 7.42, <= 7.53>= 8.49, <= 8.60>= 10.28, < 10.50CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 connected Realtek USB network adaptersRun 'lsusb' on Linux or check Device Manager on Windows for USB devices with vendor ID 0x0bda (Realtek) and product IDs corresponding to RTL8152/8153/8154/8156 chipsetsAffected if A Realtek USB Ethernet adapter with chipset RTL8152b, RTL8153, RTL8153b, RTL8154, RTL8154b, RTL8156, or RTL8156b is connected
-
Retrieve USB adapter firmware versionOn Linux, use 'lsusb -v' or check '/sys/bus/usb/devices/*/version'; on Windows, check the driver properties in Device Manager under the USB Network AdapterAffected if The firmware version matches any of these ranges: 7.42-7.53, 8.49-8.60, or 10.28-10.49
-
Confirm network exposure of the adapterCheck if the USB adapter is configured with an IP address on a local network accessible to unauthenticated attackers. Use 'ip addr show' (Linux) or 'ipconfig' (Windows) to list active network interfacesAffected if The affected adapter has an active network interface on a local network where untrusted devices or users can communicate with it
A user is affected if they have a Realtek USB Ethernet adapter (RTL8152b/8153/8153b/8154/8154b/8156/8156b) with firmware version 7.42-7.53, 8.49-8.60, or 10.28-10.49 connected and configured on a network
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.
dbcve · scoped10.50
Apply the vendor-supplied patch or updated Realtek USB driver that implements proper parameter length verification in the affected API function.
Firmware version 10.50 or later for the affected RTL815x chip families
- Identify the exact firmware version of the affected Realtek network adapter using the device management interface or system utilities.
- Navigate to the official Realtek or device manufacturer support website to obtain the firmware update.
- Download the firmware version 10.50 or later (as the last affected range ends at <10.50), ensuring it matches your specific chip model (Rtl8156, Rtl8156b, Rtl8153, Rtl8153b, Rtl8154, Rtl8154b, or Rtl8152b).
- Follow the manufacturer's firmware flashing instructions, typically involving a reboot and the use of a firmware update utility or web-based management interface.
- After updating, verify the firmware version has been successfully changed to a version >= 10.50.
- Restart the device to ensure the new firmware is fully initialized.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,256.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21742 — 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-2022-21742 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