LiveActive security incident?Get immediate response
CVE Record

CVE-2024-56718: net/smc: protect link down work from execute after lgr freed

In the Linux kernel, the following vulnerability has been resolved: net/smc: protect link down work from execute after lgr freed link down work may be scheduled before lgr freed but execute after lgr freed, which may result in crash. So it is need to hold a reference before shedule link down work, and put the reference after work executed or canceled. The relevant crash call stack as follows: list_del corruption. prev->next should be ffffb638c9c0fe20, but was 0000000000000000 ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:51! invalid opcode: 0000 [#1] SMP NOPTI CPU: 6 PID: 978112 Comm: kworker/6:119 Kdump: loaded Tainted: G #1 Hardware name: Alibaba Cloud Alibaba Cloud ECS, BIOS 2221b89 04/01/2014 Workqueue: events smc_link_down_work [smc] RIP: 0010:__list_del_entry_valid.cold+0x31/0x47 RSP: 0018:ffffb638c9c0fdd8 EFLAGS: 00010086 RAX: 0000000000000054 RBX: ffff942fb75e5128 RCX: 0000000000000000 RDX: ffff943520930aa0 RSI: ffff94352091fc80 RDI: ffff94352091fc80 RBP: 0000000000000000 R08: 0000000000000000 R09: ffffb638c9c0fc38 R10: ffffb638c9c0fc30 R11: ffffffffa015eb28 R12: 0000000000000002 R13: ffffb638c9c0fe20 R14: 0000000000000001 R15: ffff942f9cd051c0 FS: 0000000000000000(0000) GS:ffff943520900000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f4f25214000 CR3: 000000025fbae004 CR4: 00000000007706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: rwsem_down_write_slowpath+0x17e/0x470 smc_link_down_work+0x3c/0x60 [smc] process_one_work+0x1ac/0x350 worker_thread+0x49/0x2f0 ? rescuer_thread+0x360/0x360 kthread+0x118/0x140 ? __kthread_bind_mask+0x60/0x60 ret_from_fork+0x1f/0x30

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A timing flaw in the Linux kernel's SMC networking code can let queued link-down work access an already-freed link group, causing kernel corruption and a system crash. The supplied record rates it critical, although the public technical description demonstrates availability impact and does not establish data theft or modification.

Executive priority

Treat this as an expedited availability-risk update for SMC-enabled Linux infrastructure, especially critical or highly available systems. Do not infer universal internet exposure from the CVSS vector alone. First identify actual SMC use, then apply supported kernel updates according to operational criticality and vendor guidance.

Technical view

CVE-2024-56718 is a lifetime-management race in net/smc. Link-down work can be scheduled before an SMC link group is freed but execute afterward. The stable fix holds a reference while work is pending and releases it after execution or cancellation. The supplied crash shows list corruption and a kernel BUG in smc_link_down_work.

Likely exposure

Exposure is limited to Linux systems using the affected SMC networking path. The bundle lists Linux 5.8, 6.1.122, 6.6.68, 6.12.7, and 6.13 as affected values, but its version-range semantics are incomplete. Confirm the exact vendor kernel build and whether SMC is present and operational.

Exploitation context

The supplied record says this race may crash the kernel. It provides no evidence of public exploitation, exploit availability, or reliable confidentiality and integrity impact. The CVE is not listed as KEV in the bundle. Preconditions and remote triggerability are not sufficiently documented here, despite the supplied CVSS 9.8 network vector.

Researcher notes

The evidence supports a use-after-free-style asynchronous work race and reproducible kernel crash. It does not establish code execution, data disclosure, integrity compromise, or active exploitation. The affected-version data includes ambiguous values and duplicate commit identifiers, so distribution-specific backport analysis is necessary before declaring a host vulnerable.

Mitigation direction

  • Install a vendor-supported kernel containing the referenced stable fix.
  • Prioritize systems where SMC networking is enabled or actively used.
  • Check distribution advisories for corrected package versions and reboot requirements.
  • If patching is delayed, seek vendor guidance on safely disabling unused SMC functionality.

Validation and detection

  • Inventory running kernel versions and distribution package revisions.
  • Determine whether SMC modules and networking paths are enabled or used.
  • Map vendor kernel builds to the referenced stable commits or advisories.
  • After updating, verify the corrected kernel is running following any required reboot.
  • Monitor kernel logs for smc_link_down_work crashes, list corruption, or kernel BUG events.
Prepared
Confidence
medium
Sources
7

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.

cve · low confidence lookup

CVE-2024-56718 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.

2CVSS vectors
3Timeline events
2ADP providers
6Source links

SSVC decision data

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

CVSS vector scores

2 official scores

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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Linux
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2024-56718Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
LinuxLinux541afa10c126b6c22c2a805a559c70cc41fd156e, 541afa10c126b6c22c2a805a559c70cc41fd156e, 541afa10c126b6c22c2a805a559c70cc41fd156e, 541afa10c126b6c22c2a805a559c70cc41fd156eunaffected
LinuxLinux5.8, 0, 6.1.122, 6.6.68, 6.12.7, 6.13affected
Weakness

CWE details

No CWE listed

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