Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-40983: tipc: force a dst refcount before doing decryption

Noroxi assessment

Priority: Monitor (action score 22/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.88% (FIRST EPSS); higher than 59.1% of all records.
  • Someone with local access to the system 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 2ebe8f840c7450ecbfca9d18ac92e9ce9155e269, 3eb1b39627892c4e26cb0162b75725aa5fcc60c8, 623c90d86a61e3780f682b32928af469c66ec4c2.
  • Severity is disputed: the assigning authority (CNA) scores it 9.8, NVD 5.5.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 2ebe8f840c7450ecbfca9d18ac92e9ce9155e269, 3eb1b39627892c4e26cb0162b75725aa5fcc60c8, 623c90d86a61e3780f682b32928af469c66ec4c2 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: tipc: force a dst refcount before doing decryption As it says in commit 3bc07321ccc2 ("xfrm: Force a dst refcount before entering the xfrm type handlers"): "Crypto requests might return asynchronous. In this case we leave the rcu protected region, so force a refcount on the skb's destination entry before we enter the xfrm type input/output handlers." On TIPC decryption path it has the same problem, and skb_dst_force() should be called before doing decryption to avoid a possible crash. Shuang reported this issue when this warning is triggered: [] WARNING: include/net/dst.h:337 tipc_sk_rcv+0x1055/0x1ea0 [tipc] [] Kdump: loaded Tainted: G W --------- - - 4.18.0-496.el8.x86_64+debug [] Workqueue: crypto cryptd_queue_worker [] RIP: 0010:tipc_sk_rcv+0x1055/0x1ea0 [tipc] [] Call Trace: [] tipc_sk_mcast_rcv+0x548/0xea0 [tipc] [] tipc_rcv+0xcf5/0x1060 [tipc] [] tipc_aead_decrypt_done+0x215/0x2e0 [tipc] [] cryptd_aead_crypt+0xdb/0x190 [] cryptd_queue_worker+0xed/0x190 [] process_one_work+0x93d/0x17e0

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jul 12, 2024
Updated
Aug 5, 2026
EPSS
0.8% · 59th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.8%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
9.8
4.3 point gap

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

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-40983

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 kernel5.5 and later · before 5.10.221
  • linux linux kernel5.11 and later · before 5.15.162
  • linux linux kernel5.16 and later · before 6.1.96
  • linux linux kernel6.2 and later · before 6.6.36
  • linux linux kernel6.7 and later · before 6.9.7
  • linux linux kernel6.10

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.5affected
    • fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 and later · before 3eb1b39627892c4e26cb0162b75725aa5fcc60c8affected · git
    • fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 and later · before 692803b39a36e63ac73208e0a3769ae6a2f9bc76affected · git
    • fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 and later · before 623c90d86a61e3780f682b32928af469c66ec4c2affected · git
    • fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 and later · before b57a4a2dc8746cea58a922ebe31b6aa629d69d93affected · git
    • fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 and later · before 6808b41371670c51feea14f63ade211e78100930affected · git
    • fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 and later · before 2ebe8f840c7450ecbfca9d18ac92e9ce9155e269affected · git
    • before 5.5not affected · semver
    • 5.10.221 and later · up to and including 5.10.*not affected · semver
    • 5.15.162 and later · up to and including 5.15.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:8kernel-rtbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-modules-extrabefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
Debian:12linuxbefore 6.1.99-16.1.99-1
Debian:13linuxbefore 6.9.7-16.9.7-1
openSUSE:Leap 15.5kernel-azurebefore 5.14.21-150500.33.69.15.14.21-150500.33.69.1
openSUSE:Leap 15.5kernel-rt_debugbefore 5.14.21-150500.13.73.15.14.21-150500.13.73.1
openSUSE:Leap 15.5kernel-source-azurebefore 5.14.21-150500.33.69.15.14.21-150500.33.69.1
openSUSE:Leap 15.5kernel-source-rtbefore 5.14.21-150500.13.73.15.14.21-150500.13.73.1
openSUSE:Leap 15.5kernel-syms-azurebefore 5.14.21-150500.33.69.15.14.21-150500.33.69.1
openSUSE:Leap 15.5kernel-syms-rtbefore 5.14.21-150500.13.73.15.14.21-150500.13.73.1
openSUSE:Leap 15.6dtb-aarch64before 6.4.0-150600.23.25.16.4.0-150600.23.25.1
openSUSE:Leap 15.6kernel-64kbbefore 6.4.0-150600.23.25.16.4.0-150600.23.25.1
openSUSE:Leap 15.6kernel-azurebefore 6.4.0-150600.8.14.16.4.0-150600.8.14.1
openSUSE:Leap 15.6kernel-debugbefore 6.4.0-150600.23.25.16.4.0-150600.23.25.1
openSUSE:Leap 15.6kernel-defaultbefore 6.4.0-150600.23.25.16.4.0-150600.23.25.1
openSUSE:Leap 15.6kernel-default-basebefore 6.4.0-150600.23.25.1.150600.12.10.26.4.0-150600.23.25.1.150600.12.10.2

+96

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-40977Jul 12, 2024 · wifi: mt76: mt7921s: fix potential hung tasks during chip recovery
    22Monitor
  • ← EarlierCVE-2024-40981Jul 12, 2024 · batman-adv: bypass empty buckets in batadv_purge_orig_ref()
    22Monitor
  • Later →CVE-2024-40985Jul 12, 2024 · net/tcp_ao: Don't leak ao_info on error-path
    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 Linux2ebe8f840c7450ecbfca9d18ac92e9ce9155e269Vendor (CNA)
Linux Linux3eb1b39627892c4e26cb0162b75725aa5fcc60c8Vendor (CNA)
Linux Linux623c90d86a61e3780f682b32928af469c66ec4c2Vendor (CNA)
Linux Linux6808b41371670c51feea14f63ade211e78100930Vendor (CNA)
Linux Linux692803b39a36e63ac73208e0a3769ae6a2f9bc76Vendor (CNA)
Linux Linuxb57a4a2dc8746cea58a922ebe31b6aa629d69d93Vendor (CNA)
almalinux:bpftool4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt4.18.0-553.27.1.rt7.368.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-core4.18.0-553.27.1.rt7.368.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug4.18.0-553.27.1.rt7.368.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-core4.18.0-553.27.1.rt7.368.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-devel4.18.0-553.27.1.rt7.368.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules4.18.0-553.27.1.rt7.368.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules-extra4.18.0-553.27.1.rt7.368.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-devel4.18.0-553.27.1.rt7.368.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules4.18.0-553.27.1.rt7.368.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules-extra4.18.0-553.27.1.rt7.368.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.99-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch646.4.0-150600.23.25.1 · openSUSE:Leap 15.6Package registry (OSV)

+38

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

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

  • Someone with local access to the system 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
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 (6 more)

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

All records