Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-47659: smack: tcp: ipv4, fix incorrect labeling

Noroxi assessment

Priority: Monitor (action score 35/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: 0.77% (FIRST EPSS); higher than 56% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0776bcf9cb6de46fdd94d10118de1cf9b05f83b9, 0aea09e82eafa50a373fc8a4b84c1d4734751e2c, 2fe209d0ad2e2729f7e22b9b31a86cc3ff0db550.

Low priority for now. Upgrade to Linux Linux 0776bcf9cb6de46fdd94d10118de1cf9b05f83b9, 0aea09e82eafa50a373fc8a4b84c1d4734751e2c, 2fe209d0ad2e2729f7e22b9b31a86cc3ff0db550 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: smack: tcp: ipv4, fix incorrect labeling Currently, Smack mirrors the label of incoming tcp/ipv4 connections: when a label 'foo' connects to a label 'bar' with tcp/ipv4, 'foo' always gets 'foo' in returned ipv4 packets. So, 1) returned packets are incorrectly labeled ('foo' instead of 'bar') 2) 'bar' can write to 'foo' without being authorized to write. Here is a scenario how to see this: * Take two machines, let's call them C and S, with active Smack in the default state (no settings, no rules, no labeled hosts, only builtin labels) * At S, add Smack rule 'foo bar w' (labels 'foo' and 'bar' are instantiated at S at this moment) * At S, at label 'bar', launch a program that listens for incoming tcp/ipv4 connections * From C, at label 'foo', connect to the listener at S. (label 'foo' is instantiated at C at this moment) Connection succeedes and works. * Send some data in both directions. * Collect network traffic of this connection. All packets in both directions are labeled with the CIPSO of the label 'foo'. Hence, label 'bar' writes to 'foo' without being authorized, and even without ever being known at C. If anybody cares: exactly the same happens with DCCP. This behavior 1st manifested in release 2.6.29.4 (see Fixes below) and it looks unintentional. At least, no explanation was provided. I changed returned packes label into the 'bar', to bring it into line with the Smack documentation claims.

HighCVSS 8.8 · v3.1—No exploit Fix available
Published
Oct 9, 2024
Updated
Aug 5, 2026
EPSS
0.7% · 56th percentile
CWE
—

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.7%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
8.8
CNA · Linux
9.1
0.3 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-2024-47659

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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 kernelbefore 4.19.322
  • linux linux kernel4.20 and later · before 5.4.284
  • linux linux kernel5.5 and later · before 5.10.226
  • linux linux kernel5.11 and later · before 5.15.167
  • linux linux kernel5.16 and later · before 6.1.109
  • linux linux kernel6.2 and later · before 6.6.50
  • linux linux kernel6.7 and later · before 6.10.9

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

    • 2.6.30affected
    • 07feee8f812f7327a46186f7604df312c8c81962 and later · before d3f56c653c65f170b172d3c23120bc64ada645d8affected · git
    • 07feee8f812f7327a46186f7604df312c8c81962 and later · before 5b4b304f196c070342e32a4752e1fa2e22fc0671affected · git
    • 07feee8f812f7327a46186f7604df312c8c81962 and later · before a948ec993541db4ef392b555c37a1186f4d61670affected · git
    • 07feee8f812f7327a46186f7604df312c8c81962 and later · before 0aea09e82eafa50a373fc8a4b84c1d4734751e2caffected · git
    • 07feee8f812f7327a46186f7604df312c8c81962 and later · before 0776bcf9cb6de46fdd94d10118de1cf9b05f83b9affected · git
    • 07feee8f812f7327a46186f7604df312c8c81962 and later · before 4be9fd15c3c88775bdf6fa37acabe6de85beebffaffected · git
    • 07feee8f812f7327a46186f7604df312c8c81962 and later · before d3703fa94116fed91f64c7d1c7d284fb4369070faffected · git
    • 07feee8f812f7327a46186f7604df312c8c81962 and later · before 2fe209d0ad2e2729f7e22b9b31a86cc3ff0db550affected · git
    • before 2.6.30not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.112-16.1.112-1
Debian:13linuxbefore 6.10.9-16.10.9-1

Same product

linux: all records

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-2024-46870Oct 9, 2024 · drm/amd/display: Disable DMCUB timeout for DCN35
    18Monitor
  • ← EarlierCVE-2024-46871Oct 9, 2024 · drm/amd/display: Correct the defined value for AMDGPU_DMUB_NOTIFICATION_MAX
    31Monitor
  • Later →CVE-2024-47662Oct 9, 2024 · drm/amd/display: Remove register from DCN35 DMCUB diagnostic collection
    22Monitor

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 Linux0776bcf9cb6de46fdd94d10118de1cf9b05f83b9Vendor (CNA)
Linux Linux0aea09e82eafa50a373fc8a4b84c1d4734751e2cVendor (CNA)
Linux Linux2fe209d0ad2e2729f7e22b9b31a86cc3ff0db550Vendor (CNA)
Linux Linux4be9fd15c3c88775bdf6fa37acabe6de85beebffVendor (CNA)
Linux Linux5b4b304f196c070342e32a4752e1fa2e22fc0671Vendor (CNA)
Linux Linuxa948ec993541db4ef392b555c37a1186f4d61670Vendor (CNA)
Linux Linuxd3703fa94116fed91f64c7d1c7d284fb4369070fVendor (CNA)
Linux Linuxd3f56c653c65f170b172d3c23120bc64ada645d8Vendor (CNA)
debian:linux6.1.112-1 · Debian:12Package 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.

Credits

All researchers

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).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

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

Weakness class (CWE)

—

CVSS vector

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

nvd-primary

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

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records