AEGLIX vulnerability intelligence
CVE-2026-43278
HIGH · CVSS 7.8 · Modified
Published: 2026-05-06 · Updated: 2026-11-11 · Source: NVD
Stored catalog record
Source record retrieved 2026-11-12T01:13:58.283137+00:00. Scheduled imports handle updates; this page does not assert that the provider was queried just now.
Continue your research
Connect this record to stored reporting, reviewed campaign mentions and source-domain investigation. These are research leads, not inferred attack relationships.
Open CVE research in Investigate · Find Arsenal listings referencing this CVE
Vulnerability overview
In the Linux kernel, the following vulnerability has been resolved: dm: clear cloned request bio pointer when last clone bio completes Stale rq->bio values have been observed to cause double-initialization of cloned bios in request-based device-mapper targets, leading to use-after-free and double-free scenarios. One such case occurs when using dm-multipath on top of a PCIe NVMe namespace, where cloned request bios are freed during blk_complete_request(), but rq->bio is left intact. Subsequent clone teardown then attempts to free the same bios again via blk_rq_unprep_clone(). The resulting double-free path looks like: nvme_pci_complete_batch() nvme_complete_batch() blk_mq_end_request_batch() blk_complete_request() // called on a DM clone request bio_endio() // first free of all clone bios ... rq->end_io() // end_clone_request() dm_complete_request(tio->orig) dm_softirq_done() dm_done() dm_end_request() blk_rq_unprep_clone() // second free of clone bios Fix this by clearing the clone request's bio pointer when the last cloned bio completes, ensuring that later teardown paths do not attempt to free already-released bios.
Patch review priority
Assess exposure and vendor guidance
- No higher-priority signal is available in the current stored evidence.
FIRST EPSS: 0.12% · percentile 1.7 · score date 2026-11-18.
EPSS estimates probability of exploitation in the next 30 days. It does not measure your exposure or prove exploitation. The elevated threshold is 10%; CISA KEV takes precedence. About FIRST EPSS ↗
Severity and scoring
- CVSS score
- 7.8 · HIGH
- CVSS version
- 3.1
- CVSS vector
- CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weaknesses
- CWE-415
CVSS measures technical severity; it does not establish whether this vulnerability is being exploited in your environment.
Known exploitation and remediation
Not listed in the CISA catalog retrieved for this record. This does not establish that exploitation has not occurred.
Verify affected versions and patch availability in the vendor advisory before making changes.
Affected products and versions
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
From (inclusive): 6.1
Before (exclusive): 6.1.165
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
From (inclusive): 6.2
Before (exclusive): 6.6.128
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
From (inclusive): 6.7
Before (exclusive): 6.12.75
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
From (inclusive): 6.13
Before (exclusive): 6.18.16
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
From (inclusive): 6.19
Before (exclusive): 6.19.6
These are NVD CPE applicability entries. Some products depend on configuration conditions; consult the official record to confirm applicability.
Advisories and references
- https://git.kernel.org/stable/c/7daf279c674d515fb22a727a7bbc92aeb35c5442
Patch
- https://git.kernel.org/stable/c/83d72091804600ead96dc9e9f518ea56cb4942f6
Patch
- https://git.kernel.org/stable/c/8d9ddad561136f7e6a9346767bf97b4d79e38e67
Patch
- https://git.kernel.org/stable/c/b1c1a2637ebd675aa2d71fee8c70da8791d73850
Patch
- https://git.kernel.org/stable/c/e2e738e8dfbbf83bd2bae0467ec4420cc52da42a
Patch
- https://git.kernel.org/stable/c/fb8a6c18fb9a6561f7a15b58b272442b77a242dd
Patch
- https://git.kernel.org/stable/c/3d746b639be4b4f5cd8ce2b06aa52dc443f50edc
Patch
- https://git.kernel.org/stable/c/9a95b98202113045bc1a5bcb30388a500f25e050
Patch