Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2021-47241: ethtool: strset: fix message length calculation

Noroxi assessment

Priority: Monitor (action score 30/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 63.9% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Linux Linux cfc7f0e70d649e6d2233fba0d9390b525677d971, e175aef902697826d344ce3a12189329848fe898, fb3a948143688e14e2cfd2a2812877923d0e5e92.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux cfc7f0e70d649e6d2233fba0d9390b525677d971, e175aef902697826d344ce3a12189329848fe898, fb3a948143688e14e2cfd2a2812877923d0e5e92 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: ethtool: strset: fix message length calculation Outer nest for ETHTOOL_A_STRSET_STRINGSETS is not accounted for. This may result in ETHTOOL_MSG_STRSET_GET producing a warning like: calculated message payload length (684) not sufficient WARNING: CPU: 0 PID: 30967 at net/ethtool/netlink.c:369 ethnl_default_doit+0x87a/0xa20 and a splat. As usually with such warnings three conditions must be met for the warning to trigger: - there must be no skb size rounding up (e.g. reply_size of 684); - string set must be per-device (so that the header gets populated); - the device name must be at least 12 characters long. all in all with current user space it looks like reading priv flags is the only place this could potentially happen. Or with syzbot :)

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
May 21, 2024
Updated
Jun 17, 2026
EPSS
1.0% · 63th percentile

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.0%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2021-47241

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.6 and later · before 5.10.46
  • linux linux kernel5.11 and later · before 5.12.13
  • linux linux kernel5.13

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.6affected
    • 71921690f9745fef60a2bad425f30adf8cdc9da0 and later · before fb3a948143688e14e2cfd2a2812877923d0e5e92affected · git
    • 71921690f9745fef60a2bad425f30adf8cdc9da0 and later · before cfc7f0e70d649e6d2233fba0d9390b525677d971affected · git
    • 71921690f9745fef60a2bad425f30adf8cdc9da0 and later · before e175aef902697826d344ce3a12189329848fe898affected · git
    • before 5.6not affected · semver
    • 5.10.46 and later · up to and including 5.10.*not affected · semver
    • 5.12.13 and later · up to and including 5.12.*not affected · semver
    • 5.13 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.10.46-15.10.46-1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-64kbbefore 5.3.18-150300.59.164.15.3.18-150300.59.164.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-default-basebefore 5.3.18-150300.59.164.1.150300.18.96.15.3.18-150300.59.164.1.150300.18.96.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-docsbefore 5.3.18-150300.59.164.15.3.18-150300.59.164.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-obs-buildbefore 5.3.18-150300.59.164.15.3.18-150300.59.164.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-preemptbefore 5.3.18-150300.59.164.15.3.18-150300.59.164.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-sourcebefore 5.3.18-150300.59.164.15.3.18-150300.59.164.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-symsbefore 5.3.18-150300.59.164.15.3.18-150300.59.164.1
SUSE:Linux Enterprise Live Patching 15 SP3kernel-defaultbefore 5.3.18-150300.59.164.15.3.18-150300.59.164.1
SUSE:Linux Enterprise Live Patching 15 SP3kernel-livepatch-SLE15-SP3_Update_45before 1-150300.7.3.11-150300.7.3.1
SUSE:Linux Enterprise Micro 5.1kernel-rtbefore 5.3.18-150300.172.15.3.18-150300.172.1
SUSE:Linux Enterprise Micro 5.1kernel-source-rtbefore 5.3.18-150300.172.15.3.18-150300.172.1
SUSE:Linux Enterprise Server 15 SP3-LTSSkernel-zfcpdumpbefore 5.3.18-150300.59.164.15.3.18-150300.59.164.1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2021-47239May 21, 2024 · net: usb: fix possible use-after-free in smsc75xx_bind
    31Monitor
  • ← EarlierCVE-2021-47240May 21, 2024 · net: qrtr: fix OOB Read in qrtr_endpoint_post
    28Monitor
  • Later →CVE-2021-47242May 21, 2024 · mptcp: fix soft lookup in subflow_error_report()
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linuxcfc7f0e70d649e6d2233fba0d9390b525677d971Vendor (CNA)
Linux Linuxe175aef902697826d344ce3a12189329848fe898Vendor (CNA)
Linux Linuxfb3a948143688e14e2cfd2a2812877923d0e5e92Vendor (CNA)
debian:linux5.10.46-1 · Debian:12Package registry (OSV)
suse:kernel-64kb5.3.18-150300.59.164.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-default5.3.18-150300.59.164.1 · SUSE:Linux Enterprise Live Patching 15 SP3Package registry (OSV)
suse:kernel-default-base5.3.18-150300.59.164.1.150300.18.96.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-docs5.3.18-150300.59.164.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-livepatch-SLE15-SP3_Update_451-150300.7.3.1 · SUSE:Linux Enterprise Live Patching 15 SP3Package registry (OSV)
suse:kernel-obs-build5.3.18-150300.59.164.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-preempt5.3.18-150300.59.164.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-rt5.3.18-150300.172.1 · SUSE:Linux Enterprise Micro 5.1Package registry (OSV)
suse:kernel-source5.3.18-150300.59.164.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-source-rt5.3.18-150300.172.1 · SUSE:Linux Enterprise Micro 5.1Package registry (OSV)
suse:kernel-syms5.3.18-150300.59.164.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-zfcpdump5.3.18-150300.59.164.1 · SUSE:Linux Enterprise Server 15 SP3-LTSSPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records