Home/CVE/In the Linux kernel, the following vulnerability has been resolved: crypto: algif_aead - Fix minimum RX size check for
CVE

CVE-2026-43077

In the Linux kernel, the following vulnerability has been resolved: crypto: algif_aead - Fix minimum RX size check for

In the Linux kernel, the following vulnerability has been resolved: crypto: algif_aead - Fix minimum RX size check for decryption The check for the minimum receive buffer size did not take the tag size into account during decryption. Fix this by adding the required extra length.

MEDIUM · CVSS 5.5 EPSS 0.00015
Monitor
  • No active-exploitation, high-EPSS, or public-exploit signals - routine patching cadence
Sigma rules0 YARA rules0
Look this up elsewhere - one-click external pivots
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2026-43077, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).

ATT&CK techniques

1

Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.

▤ Build a SIEM detection for these techniques

Affected Products & Versions

8
linux kernel>= 4.14.1 and < 5.10.254
linux kernel>= 5.11 and < 5.15.204
linux kernel>= 5.16 and < 6.1.170
linux kernel>= 6.2 and < 6.6.136
linux kernel>= 6.7 and < 6.12.83
linux kernel>= 6.13 and < 6.18.24
linux kernel>= 6.19 and < 6.19.14
linux kernelall versions
📦

Fixed versions by distribution

80
The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
oracle allkernel-uek fixed in 0:5.4.17-2136.355.3.1.el7uek
oracle allkernel-uek-container fixed in 0:5.4.17-2136.355.3.1.el7uek
oracle allkernel-uek-container-debug open
oracle allkernel-uek-debug open
oracle allkernel-uek-debug-devel fixed in 0:5.4.17-2136.355.3.1.el8uek
oracle allkernel-uek-devel open
oracle allkernel-uek-tools open
rhel 8bpftool open
rhel 8kernel open
rhel 8kernel-abi-stablelists fixed in 0:4.18.0-553.123.1.el8_10
rhel 8kernel-core fixed in 0:4.18.0-553.123.1.el8_10
rhel 8kernel-debug open
rhel 8kernel-debug-core fixed in 0:4.18.0-553.123.1.el8_10
rhel 8kernel-debug-devel fixed in 0:4.18.0-553.123.1.el8_10
rhel 8kernel-debug-modules fixed in 0:4.18.0-553.123.1.el8_10
rhel 8kernel-debug-modules-extra open
rhel 8kernel-devel open
rhel 8kernel-modules fixed in 0:4.18.0-553.123.1.el8_10
rhel 8kernel-modules-extra open
rhel 8kernel-rt open
rhel 8kernel-rt-core open
rhel 8kernel-rt-debug open
rhel 8kernel-rt-debug-core fixed in 0:4.18.0-553.123.1.rt7.464.el8_10
rhel 8kernel-rt-debug-devel open
rhel 8kernel-rt-debug-kvm fixed in 0:4.18.0-553.123.1.rt7.464.el8_10
rhel 8kernel-rt-debug-modules open
rhel 8kernel-rt-debug-modules-extra fixed in 0:4.18.0-553.123.1.rt7.464.el8_10
rhel 8kernel-rt-devel open
rhel 8kernel-rt-kvm open
rhel 8kernel-rt-modules open
rhel 8kernel-rt-modules-extra open
rhel 8kernel-tools fixed in 0:4.18.0-553.123.1.el8_10
rhel 8kernel-tools-libs open
rhel 8kernel-tools-libs-devel open
rhel 8kernel-zfcpdump open
rhel 8kernel-zfcpdump-core open
rhel 8kernel-zfcpdump-devel open
rhel 8kernel-zfcpdump-modules open
rhel 8kernel-zfcpdump-modules-extra open
rhel 8perf fixed in 0:4.18.0-553.123.1.el8_10
rhel 8python3-perf open
rhel 9kernel fixed in 0:5.14.0-611.54.1.el9_7
rhel 9kernel-64k fixed in 0:5.14.0-611.54.1.el9_7
rhel 9kernel-64k-core open
rhel 9kernel-64k-debug open
rhel 9kernel-64k-debug-core fixed in 0:5.14.0-611.54.1.el9_7
rhel 9kernel-64k-debug-devel open
rhel 9kernel-64k-debug-devel-matched open
rhel 9kernel-64k-debug-modules fixed in 0:5.14.0-611.54.1.el9_7
rhel 9kernel-64k-debug-modules-core open
rhel 9kernel-64k-debug-modules-extra open
rhel 9kernel-64k-devel fixed in 0:5.14.0-611.54.1.el9_7
rhel 9kernel-64k-devel-matched open
rhel 9kernel-64k-modules fixed in 0:5.14.0-611.54.1.el9_7
rhel 9kernel-64k-modules-core fixed in 0:5.14.0-611.54.1.el9_7
rhel 9kernel-64k-modules-extra open
rhel 9kernel-abi-stablelists fixed in 0:5.14.0-611.54.1.el9_7
rhel 9kernel-core open
rhel 9kernel-debug fixed in 0:5.14.0-611.54.1.el9_7
rhel 9kernel-debug-core open
rhel 9kernel-debug-devel open
rhel 9kernel-debug-devel-matched fixed in 0:5.14.0-611.54.1.el9_7
rhel 9kernel-debug-modules fixed in 0:5.14.0-611.54.1.el9_7
rhel 9kernel-debug-modules-core open
rhel 9kernel-debug-modules-extra open
rhel 9kernel-debug-uki-virt open
rhel 9kernel-devel fixed in 0:5.14.0-611.54.1.el9_7
rhel 9kernel-devel-matched fixed in 0:5.14.0-611.54.1.el9_7
rhel 9kernel-modules fixed in 0:5.14.0-611.54.1.el9_7
rhel 9kernel-modules-core open
rhel 9kernel-modules-extra fixed in 0:5.14.0-611.54.1.el9_7
rhel 9kernel-rt open
rhel 9kernel-rt-64k open
rhel 9kernel-rt-64k-core fixed in 0:5.14.0-611.54.1.el9_7
rhel 9kernel-rt-64k-debug open
rhel 9kernel-rt-64k-debug-core fixed in 0:5.14.0-611.54.1.el9_7
rhel 9kernel-rt-64k-debug-devel fixed in 0:5.14.0-611.54.1.el9_7
rhel 9kernel-rt-64k-debug-modules open
rhel 9kernel-rt-64k-debug-modules-core fixed in 0:5.14.0-611.54.1.el9_7
rhel 9kernel-rt-64k-debug-modules-extra open

Scoring & Timeline

5.5
MEDIUM · CVSS v3.1 · 416baaa9-dc9f-4396-8d5f-8c081fb06d67
View on NVD
Attack Vector
Network Adjacent Local Physical
Attack Complexity
Low High
Privileges Required
None Low High
User Interaction
None Required
Scope
Unchanged Changed
Confidentiality
None Low High
Integrity
None Low High
Availability
None Low High
Published to NVD06 May 2026 · 10:16 AM
CVSS VectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
SOC and Response
CVE triage
Stack monitoring
Am I affected
IOC triage
KEV catalog
Recently exploited
Daily brief
Change tracking
Detection Engineering
Coverage workspace
Detection coverage
Coverage check
Telemetry ceiling
SIEM query builder
Sigma rules
SIEM rules
YARA rules
Network rules
D3FEND
Threat Hunting
Threat actors
ATT&CK techniques
Attack paths
Indicators
Atomic tests
Red Team and Pentest
Exploitability triage
Recon pack
Attack paths
CAPEC patterns
Adversary emulation
Compliance and GRC
Framework mapping
Control assessment
Audit view
Coverage report
Atlas Search Threat actors Techniques Tools & malware CWE CAPEC KEV catalog Package vulns
About All capabilities Pricing API docs Live status Privacy policy Terms of service
threatengine.sh