End of life / Linux Kernel / 7.3
Linux Kernel 7.3 end of life
Linux Kernel 7.3 has no published end of life date. 2 known CVEs reach this release, the most severe rated HIGH.
The detail
- Released
- 18 October 2026
- End of life
- not published
- Countdown
- no published end of life date
- Status
- No published date
- Long term support
- No
- Newest build on this release
- 7.3
- Newest release overall
- 7.3
CVEs that reach 7.3
| Advisory | Severity | CVSS | Published | Fixed in |
|---|---|---|---|---|
| CVE-2026-98136 In the Linux kernel, the following vulnerability has been resolved:
ntfs: bound $AttrDef table walk to the loaded table size
ntfs_attr_find_in_attrdef() walks the in-memory $AttrDef table, but the
loop condition bounds only the start of each entry, not the whole entry:
for (ad = vol->attrdef; (u8 *)ad - (u8 *)vol->attrdef <
vol->attrdef_size && ad->type; ++ad)
struct attr_def is 160 bytes; the guard reads ad->type at offset 128 and
the loop body reads further fields. vol->attrdef is kvza | HIGH | 7.1 | 25 September 2026 | no fixed version published |
| CVE-2026-98163 In the Linux kernel, the following vulnerability has been resolved:
cgroup: Avoid iteration of dying tasks with zero refcount
The commit 260fbcb92bbea ("cgroup: Move dying_tasks cleanup from
cgroup_task_release() to cgroup_task_free()") extended the lifetime of
tasks on the dying_tasks list.
The iterators have provision to go through dying_tasks because of
dying threadgroup leaders or explicit CSS_TASK_ITER_WITH_DEAD, however,
it was expected that such tasks can obtain a new reference (that is | HIGH | 7.0 | 26 September 2026 | no fixed version published |
A further 431 advisories publish no version range, so whether they reach 7.3 cannot be determined from the advisory alone.
Other Linux Kernel releases
Vendor sources last checked 22 October 2026, and checked daily. This data last changed on 22 October 2026.
Be told before Linux Kernel 7.3 runs out
One email, ahead of the date, and nothing else. No account, no newsletter, and every message carries a link that stops them for good.
You just looked this up by hand, for one version
You had to already know you were running this version to search for it. StackDrift scans your machines and works that out for you, across every runtime, operating system and kernel underneath your code, then mails you before the next support window closes or a CVE lands on a build you have deployed.
A card is needed to open the trial and nothing is charged until it ends.