LiveActive security incident?Get immediate response
CVE Record

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

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.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-47241 is a Linux kernel ethtool netlink bug where the kernel can underestimate a response size. Under narrow device and request conditions, this can trigger a kernel warning and splat, creating an availability concern rather than a known data theft or privilege escalation issue.

Executive priority

Treat this as a high-priority availability patch for Linux systems, especially infrastructure with network device management exposure. It is not documented here as actively exploited, but kernel availability issues deserve normal expedited remediation.

Technical view

The issue is in ethtool string-set handling: the outer ETHTOOL_A_STRSET_STRINGSETS nest was not included in message length calculation. The source says ETHTOOL_MSG_STRSET_GET can produce an insufficient payload warning when specific skb sizing, per-device string set, and long device-name conditions align.

Likely exposure

Systems running affected Linux kernel versions or unpatched vendor kernels may be exposed, especially where ethtool netlink queries against network devices are possible. Confirm exposure against kernel build, distribution backports, and the linked stable fixes.

Exploitation context

The bundle does not show CISA KEV listing or confirmed active exploitation. The description frames triggering conditions as narrow and notes current user space appears mainly relevant when reading private flags, with syzbot-style discovery also mentioned.

Researcher notes

Evidence is limited to the CVE record and kernel stable references. The described trigger requires multiple conditions, including no skb rounding, per-device string set header population, and a device name of at least 12 characters.

Mitigation direction

  • Update to a kernel containing the referenced stable ethtool strset fixes.
  • Check Linux distribution advisories for backported fixes before judging by version alone.
  • Limit unnecessary local or remote access to ethtool-capable management interfaces.
  • Monitor kernel logs for repeated ethtool netlink warning or splat patterns.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, and network-focused hosts.
  • Compare deployed kernel packages against vendor advisories and linked stable commits.
  • Review kernel logs for ETHTOOL_MSG_STRSET_GET payload length warnings.
  • Confirm whether long network device names and per-device string sets exist.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-266: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-47241 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2021-47241Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux71921690f9745fef60a2bad425f30adf8cdc9da0, 71921690f9745fef60a2bad425f30adf8cdc9da0, 71921690f9745fef60a2bad425f30adf8cdc9da0unaffected
LinuxLinux5.6, 0, 5.10.46, 5.12.13, 5.13affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-266 · source CWE mapping

Incorrect Privilege Assignment

Incorrect Privilege Assignment represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.