CVE-2026-43078: crypto: af_alg - Fix page reassignment overflow in af_alg_pull_tsgl
In the Linux kernel, the following vulnerability has been resolved:
crypto: af_alg - Fix page reassignment overflow in af_alg_pull_tsgl
When page reassignment was added to af_alg_pull_tsgl the original
loop wasn't updated so it may try to reassign one more page than
necessary.
Add the check to the reassignment so that this does not happen.
Also update the comment which still refers to the obsolete offset
argument.
Security readout for executives and security teams
Plain-English summary
A Linux kernel cryptography bug can reassign one more memory page than intended. A local, low-privileged user may be able to trigger serious confidentiality, integrity, or availability impact. The supplied record rates it 7.8 High, but does not establish real-world exploitation.
Executive priority
Treat as a high-priority kernel maintenance issue, especially on multi-user or shared-compute Linux systems. It is not supported as an emergency internet-wide threat because exploitation requires local access and active exploitation is not reported. Promptly establish inventory, obtain distribution-specific fixed-version guidance, and schedule upgrades according to local-user exposure.
Technical view
The flaw is in crypto/af_alg function af_alg_pull_tsgl. A loop omitted a boundary check after page reassignment was introduced, allowing one unnecessary page reassignment. The kernel fix adds the missing check. The supplied CVSS vector indicates local access, low complexity, low privileges, no user interaction, unchanged scope, and high impact.
Likely exposure
Exposure is limited to affected Linux kernels where an attacker already has low-privileged local access and can reach the relevant AF_ALG functionality. The supplied affected-version data is ambiguous and includes commit identifiers and loosely structured version values, so exact exposure should be confirmed against Linux or distribution advisories.
Exploitation context
The supplied record does not report active exploitation, and CVE-2026-43078 is not marked as CISA KEV. No public exploit evidence is included. Its local, low-privilege attack requirements make shared Linux systems and hosts permitting untrusted local users more concerning than systems without such access.
Researcher notes
The root cause is an off-by-one-style page reassignment condition in af_alg_pull_tsgl. Eight stable-kernel commits are referenced, indicating fixes across branches, but the bundle does not reliably map them to corrected release versions. No CWE, crash trace, proof of concept, exploitation telemetry, or detailed primitive is supplied.
Mitigation direction
Install a vendor-supported kernel containing the applicable upstream stable fix.
Consult the Linux distribution advisory for exact affected and corrected package versions.
Prioritize shared systems and hosts that permit untrusted local users.
Use normal change controls and reboot if required to activate the corrected kernel.
Validation and detection
Record each host's running kernel version and distribution package release.
Compare installed packages with authoritative Linux distribution advisories for CVE-2026-43078.
Confirm the running kernel includes the distribution backport or applicable upstream fix.
Verify systems booted into the corrected kernel after maintenance.
Monitor vendor guidance because the supplied affected-version data is not definitive.
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-2026-43078 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
1CVSS vectors
3Timeline events
0ADP providers
9Source links
CVSS vector scores
1 official score
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.