Detections
Analytics

Echo: linux: security update to 6.11.7-1

high Tenable Self-Hosted Container Security Plugin ID 459538

Description

There are packages installed that are affected by a vulnerability referenced in the following CVE:

 - In the Linux kernel, the following vulnerability has been resolved: cxl/port: Fix use-after-free, permit
 out-of-order decoder shutdown In support of investigating an initialization failure report [1], cxl_test
 was updated to register mock memory-devices after the mock root-port/bus device had been registered. That
 led to cxl_test crashing with a use-after-free bug with the following signature: cxl_port_attach_region:
 cxl region3: cxl_host_bridge.0:port3 decoder3.0 add: mem0:decoder7.0 @ 0 next: cxl_switch_uport.0 nr_eps:
 1 nr_targets: 1 cxl_port_attach_region: cxl region3: cxl_host_bridge.0:port3 decoder3.0 add:
 mem4:decoder14.0 @ 1 next: cxl_switch_uport.0 nr_eps: 2 nr_targets: 1 cxl_port_setup_targets: cxl region3:
 cxl_switch_uport.0:port6 target[0] = cxl_switch_dport.0 for mem0:decoder7.0 @ 0 1) cxl_port_setup_targets:
 cxl region3: cxl_switch_uport.0:port6 target[1] = cxl_switch_dport.4 for mem4:decoder14.0 @ 1 [..]
 cxld_unregister: cxl decoder14.0: cxl_region_decode_reset: cxl_region region3: mock_decoder_reset:
 cxl_port port3: decoder3.0 reset 2) mock_decoder_reset: cxl_port port3: decoder3.0: out of order reset,
 expected decoder3.1 cxl_endpoint_decoder_release: cxl decoder14.0: [..] cxld_unregister: cxl decoder7.0:
 3) cxl_region_decode_reset: cxl_region region3: Oops: general protection fault, probably for non-canonical
 address 0x6b6b6b6b6b6b6bc3: 0000 [#1] PREEMPT SMP PTI [..] RIP: 0010:to_cxl_port+0x8/0x60 [cxl_core] [..]
 Call Trace: <TASK> cxl_region_decode_reset+0x69/0x190 [cxl_core] cxl_region_detach+0xe8/0x210 [cxl_core]
 cxl_decoder_kill_region+0x27/0x40 [cxl_core] cxld_unregister+0x5d/0x60 [cxl_core] At 1) a region has been
 established with 2 endpoint decoders (7.0 and 14.0). Those endpoints share a common switch-decoder in the
 topology (3.0). At teardown, 2), decoder14.0 is the first to be removed and hits the "out of order reset
 case" in the switch decoder. The effect though is that region3 cleanup is aborted leaving it in-tact and
 referencing decoder14.0. At 3) the second attempt to teardown region3 trips over the stale decoder14.0
 object which has long since been deleted. The fix here is to recognize that the CXL specification places
 no mandate on in-order shutdown of switch-decoders, the driver enforces in-order allocation, and hardware
 enforces in-order commit. So, rather than fail and leave objects dangling, always remove them. In support
 of making cxl_region_decode_reset() always succeed, cxl_region_invalidate_memregion() failures are turned
 into warnings. Crashing the kernel is ok there since system integrity is at risk if caches cannot be
 managed around physical address mutation events like CXL region destruction. A new
 device_for_each_child_reverse_from() is added to cleanup port->commit_end after all dependent decoders
 have been disabled. In other words if decoders are allocated 0->1->2 and disabled 1->2->0 then
 port->commit_end only decrements from 2 after 2 has been disabled, and it decrements all the way to zero
 since 1 was disabled previously. (CVE-2024-50226)

Solution

Update the linux library and its related packages to version 6.11.7-1 or later.

See Also

https://advisory.echohq.com/cve/CVE-2024-50226

Plugin Details

Severity: High

ID: 459538

Version: Revision 1.1

Type: Local

Published: 10/2/2026

Updated: 10/2/2026

Risk Information

VPR

Risk Factor: Medium

Score: 4.9

Percentile: 57.12

CVSS v2

Risk Factor: Medium

Base Score: 6.8

Temporal Score: 5

Vector: CVSS2#AV:L/AC:L/Au:S/C:C/I:C/A:C

CVSS Score Source: CVE-2024-50226

CVSS v3

Risk Factor: High

Base Score: 7.8

Temporal Score: 6.8

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

Temporal Vector: CVSS:3.0/E:U/RL:O/RC:C

Vulnerability Information

Exploit Ease: No known exploits are available

Patch Publication Date: 9/15/2025

Vulnerability Publication Date: 11/9/2024

Reference Information

CVE: CVE-2024-50226