CVE Intelligence
Critical Memory corruption

CVE-2026-43414 — scsi: qla2xxx: Completely fix fcport double free

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Completely fix fcport double free In qla24xx_els_dcmd_iocb() sp->free is set to qla2x00_els_dcmd_sp_free(). When an error happens, this function is called by qla2x00_sp_release(), when kref_put() releases the first and the last reference. qla2x00_els_dcmd_sp_free() frees fcport by calling qla2x00_free_fcport(). Doing it one more time after kref_put() is a bad idea.

Published May 8, 2026 · Updated Oct 16, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.4% (30-day exploitation probability)+6
  • Technical severity (critical)+10
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.44%
ahead of 37% of scored CVEs · Oct 16, 2026
Affects
Linux
Linux and 1 more
CVSS base
9.8
Critical · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Linux Linux version 9b43d2884b54d415caab48878b526dfe2ae9921bversion 7861213201838480dc222634c56fb6db113d010dversion 3b9d72442adfbc9ddb0f76dd1b03977b3a578b16version ef23850940d9a52c39936d27254824ccf5e9b6bdversion 6c6bf6cacf9461f8d301cfac4f9c175d80cbcc63version cd10dee1f07a782f5aa05703c55299ca86a85ee4version b03e626bd6d3f0684f56ee1890d70fc9ca991c04version 282877633b25d67021a34169c5b5519b1d4ef65e
and 11 more version f85af9f1aa5e2f53694a6cbe72010f754b5ff862≥ 4895009c4bb72f71f2e682f1e7d2c2d96e482087 and < c0b7da13a04bd70ef6070bfb9ea85f582294560aversion 846fb9f112f618ec6ae181d8dae7961652574774≥ 5.15.154 and < 5.16≥ 6.1.84 and < 6.2≥ 6.6.24 and < 6.7≥ 6.7.12 and < 6.8≥ 6.8.3 and < 6.9version 6.9≥ 4895009c4bb72f71f2e682f1e7d2c2d96e482087 and < 4097a2afe8acc6038b71aab825430f1403decf20≥ 4895009c4bb72f71f2e682f1e7d2c2d96e482087 and < d48ea85463f5b34f7b92ea0a13eddf1ab993da7b
Vulnerable CVE Program (cve.org) e CISA ADP
Linux Linux Kernel ≥ 6.1.84 and < 6.2≥ 5.15.154 and < 5.16≥ 6.6.24 and < 6.7≥ 6.7.12 and < 6.8≥ 6.8.3 and < 6.9≥ 6.9.1 and < 6.19.9version 6.9version 6.9-rc2
and 8 more version 6.9-rc3version 6.9-rc4version 6.9-rc5version 6.9-rc6version 6.9-rc7version 7.0-rc1version 7.0-rc2version 7.0-rc3
Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
9.8 CVSS 3.1 Critical 3.9 5.9 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database
9.8 CVSS 3.1 Critical — — GitHub, Inc. via GitHub Security Advisories
9.8 CVSS 3.1 Critical — — Linux via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-415 · Double Free

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 16, 2026 · 4 reading(s) · max 0.55%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
web/proxy/WAF logsnetwork IDS/IPSendpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 16, 2026 · CVE Program (cve.org) e CISA ADP
  • Affected products added · linux/linux
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · Analyzed → Modified
    Oct 15, 2026 · NIST National Vulnerability Database
  • Affected products added · linux/linux
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 9.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    May 8, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 15, 2026 – Oct 15, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

5 on the record

Elsewhere on this site

Linux
every CVE for this vendor
Memory corruption
same class
CWE-415
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-99999 ipv4: validate checksum_start before completing checksum 1d
  • CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 1d
  • CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 2d
  • CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 2d
  • CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 2d
  • CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-43414 is "scsi: qla2xxx: Completely fix fcport double free", rated Critical. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.8 describes technical severity. EPSS 0.44% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.