EST. 2026 — Notes from real server work SYSADMIN · SECURITY · AI · DIRECTADMIN Issue 01
THE SYSADMIN ALMANAC
Home / Security Update / Ubuntu FIPS Fixes CVE-2026-74350 Rated 9.8, Requires a Reboot
Security Update

Ubuntu FIPS Fixes CVE-2026-74350 Rated 9.8, Requires a Reboot

by Ton-Or ·19 Nov 2026·8 min read
Ubuntu FIPS Fixes CVE-2026-74350 Rated 9.8, Requires a Reboot

Administrators of older Ubuntu releases using OCFS2 or FIPS should promptly check patch entitlements and schedule a reboot. For cloud systems, compare fixed versions against the kernel flavor actually in use.

1-minute summary

Symptom / problem
OCFS2 อ่าน fast symlink ที่มี metadata ผิดรูปแล้วอ่านหน่วยความจำเกินขอบเขต และมีแพตช์ช่องโหว่ kernel อื่นรวมอยู่ในประกาศชุดเดียวกัน
Who should read
Ubuntu 16.04 ที่ใช้ linux-fips และ Ubuntu 14.04/16.04/18.04/20.04 เฉพาะสาย kernel ที่ USN-9161-1 ถึง USN-9164-1 ระบุ
Fix in short
รับแพตช์ผ่าน Ubuntu Pro และบริการที่ตรงกับรุ่น ตรวจโมดูลภายนอก แล้วรีบูตเข้า kernel ใหม่ โดยติดตามสถานะ CVE ที่ยังไม่ตรงกับ USN
Jump to steps

I noticed that Ubuntu published USN-9161-1 through USN-9164-1 dated 19 Nov. 2026, so I have brought the patches for older releases and cloud systems together here. The part I want to highlight is linux-fips on Ubuntu 16.04, which fixes CVE-2026-74350, rated 9.8 under CVSS 3.1; the OCFS2 conditions also need to be considered.

9.8CVSS 3.1 for CVE-2026-74350
OCFS2kernel reads a malformed fast symlink
16.04 FIPSAdditional patches under USN-9164-1
RebootRequired after updating in every notice

What happened in OCFS2

OCFS2 can store a short symlink target in an inode. This bug occurs when the inode specifies a target size larger than the available storage, or there is no terminating NUL at i_size, causing the kernel to read beyond the inode buffer while copying data. The patch adds inode checks and rejects malformed data before reading the symlink, as shown in the Linux patch.

This bug can occur when the kernel reads a malformed fast symlink on OCFS2, but the sources I checked do not explain how an attacker could introduce this metadata into the system. I therefore would not conclude from the score that it can be exploited over HTTP or used for unauthenticated remote code execution.

OCFS2 inodeMalformed fast symlinkRead targetInvalid size or NULBuffer overreadPath before patchingPatch checks inode before allowing readsReject oversized or improperly terminated targets
This diagram shows filesystem conditions; it does not show how an attacker could deliver data over the network.

How high is the score, and has exploitation been confirmed?

Ubuntu assigns CVE-2026-74350 a priority of High, showing a CVSS 3.1 score of 9.8 Critical with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

The same page also shows a CVSS 4.0 score of 7.1 High with the vector CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

When citing a score, specify the CVSS version and read the conditions of the bug alongside it. Details are available in the Linux CVE Record.

These Ubuntu notices do not state that CVE-2026-74350 has been exploited in the wild. This CVE is also not yet in KEV as of 18 Nov. 2026, according to the KEV JSON in CISA's official repository, so there is no CISA date added or remediation deadline for it. Absence from KEV does not mean there has been no exploitation.

The USN and CVE page still show different statuses

USN-9164-1 lists 4.4.0-1133.140 as the fixed version for Ubuntu 16.04 FIPS, but the CVE page still shows Vulnerable and work in progress for that same version. These two pages are still inconsistent. Use the USN to plan the update and check that packages are available to install, while following Canonical for confirmation of the status.

Who needs to compare versions, and what else do the patches include?

This table uses kernel image package versions from the USNs. These numbers differ from metapackage versions and the output of uname -r; match the release and flavor as well. Each USN fixes a different set of CVEs, and this table does not mean that every version has CVE-2026-74350.

Ubuntu kernel / flavor Image version in the notice USN
14.04 4.4 generic, lowlatency from Xenial HWE 4.4.0-292.326~14.04.1 9163-1
14.04 4.4 aws 4.4.0-1163.169 9163-1
16.04 4.4 generic, lowlatency 4.4.0-292.326 9163-1
16.04 4.4 aws 4.4.0-1201.216 9163-1
16.04 4.4 kvm 4.4.0-1164.175 9163-1
16.04 4.4 fips 4.4.0-1133.140 9164-1
18.04 5.4 HWE generic, lowlatency 5.4.0-246.266~18.04.1 9161-1
18.04 5.4 aws 5.4.0-1168.179~18.04.1 9161-1
18.04 5.4 azure 5.4.0-1173.179~18.04.1 9161-1
18.04 5.4 gcp 5.4.0-1171.181~18.04.1 9161-1
18.04 5.4 oracle 5.4.0-1166.176~18.04.1 9161-1
18.04 5.4 ibm 5.4.0-1114.119~18.04.1 9161-1
18.04 5.4 raspi 5.4.0-1150.163~18.04.1 9161-1
20.04 5.4 generic, generic-lpae, lowlatency 5.4.0-246.266 9161-1
20.04 5.4 aws 5.4.0-1168.179 9161-1
20.04 5.4 azure 5.4.0-1173.179 9162-1
20.04 5.4 oracle 5.4.0-1166.176 9162-1
20.04 5.4 gcp 5.4.0-1171.181 9161-1
20.04 5.4 ibm 5.4.0-1114.119 9161-1
20.04 5.4 kvm 5.4.0-1155.164 9161-1
20.04 5.4 fips 5.4.0-1142.152 9161-1
20.04 5.4 aws-fips 5.4.0-1168.179+fips1 9161-1
20.04 5.4 azure-fips 5.4.0-1173.179+fips1 9161-1
20.04 5.4 gcp-fips 5.4.0-1171.181+fips1 9161-1
20.04 5.4 bluefield 5.4.0-1127.134 9161-1
20.04 5.4 iot 5.4.0-1072.75 9161-1
20.04 5.4 raspi 5.4.0-1150.163 9161-1
20.04 5.4 xilinx-zynqmp 5.4.0-1086.90 9161-1

Ubuntu 18.04/20.04 in these notices require Ubuntu Pro, while 14.04/16.04 in USN-9163-1 also require the Legacy Support add-on. FIPS packages in USN-9161-1 and USN-9164-1 use the FIPS Updates channel through Ubuntu Pro; check that the service matching the packages in use is enabled. Using FIPS alone does not mean patches will arrive automatically.

USN-9164-1 includes CVE-2026-74350 and 19 other entries, covering Xen frontend, drivers, filesystems, and networking. The following table lists the remaining entries in References; an individual machine may not use all of these modules.

Number group Other CVEs in USN-9164-1
2026 CVE-2026-43456
2025 CVE-2025-39743, CVE-2025-39691, CVE-2025-38604, CVE-2025-21664
2024 CVE-2024-57904, CVE-2024-56779, CVE-2024-56763, CVE-2024-56616, CVE-2024-56570, CVE-2024-53214, CVE-2024-53210, CVE-2024-53194
2023 / 2022 CVE-2023-52784, CVE-2022-49170, CVE-2022-49058, CVE-2022-23037, CVE-2022-23036
2021 CVE-2021-47633

USN-9161-1 lists CVE-2025-39689, CVE-2025-39691, and CVE-2025-39726, while USN-9162-1 lists the latter two, and USN-9163-1 lists CVE-2025-39691 in References even though the Details section does not include the number.

CVE-2025-39689 is a use-after-free in ftrace. Ubuntu states that root privileges or CAP_SYS_ADMIN are required to access the relevant tracefs files.

CVE-2025-39691 is a bug when reading a filesystem buffer, while CVE-2025-39726 results from s390 ISM handling concurrent commands incorrectly, which can disconnect connections.

All three CVE pages still show work in progress for some packages at the same versions listed as fixed in the USNs. The information remains inconsistent, so check both the notices and the packages available to install.

This set patches different releases and flavors from USN-9160-1 for Ubuntu 24.04 Azure on the 7.0 series. The related article is Debian and Ubuntu security updates for 19 Nov.; patches need to be checked separately for each group in use.

How to update the kernel actually in use

Check the Ubuntu release, kernel, and installed packages, then see whether any OCFS2 filesystems are mounted. Finding none still does not establish that the machine cannot use OCFS2.

cat /etc/os-release
uname -r
dpkg-query -W -f='${binary:Package}\t${Version}\t${db:Status-Abbrev}\n' 'linux-image*'
findmnt -t ocfs2
if command -v pro >/dev/null 2>&1; then
  pro status
elif command -v ua >/dev/null 2>&1; then
  ua status
fi
  1. Match the release and flavor Check the image and metapackage actually in use, along with Pro, Legacy Support, or FIPS Updates entitlements.
  2. Prepare the maintenance window Check boot space, back up data, and prepare console access for boot recovery.
  3. Check the update plan Review packages to be added or removed and external modules that need rebuilding.
  4. Install and reboot Check the running kernel and test services before closing the maintenance window.

Once patch entitlements and repositories are ready, simulate the update and review the list first, because dist-upgrade can remove packages, as described in the apt-get manual.

sudo apt-get update
sudo apt-get -s dist-upgrade
# หลังตรวจรายการเพิ่ม/ลบ และพร้อมเข้ารอบบำรุงรักษา
sudo apt-get dist-upgrade

Every USN in this set warns that the ABI has changed and external kernel modules must be recompiled and reinstalled. Before rebooting, check DKMS and hardware vendor modules, particularly those used for disks and networking. Make sure the modules are ready for the new kernel; this still needs checking even if the image installs successfully.

if command -v dkms >/dev/null 2>&1; then
  dkms status
fi
# หลังยืนยันว่าโมดูลสำหรับ kernel ใหม่พร้อม และอยู่ในรอบรีบูต
sudo reboot

After rebooting, check the running kernel and full package version against the table.

uname -r
dpkg-query -W -f='${binary:Package}\t${Version}\n' "linux-image-$(uname -r)"
Keep the FIPS update path aligned with requirements

Canonical recommends fips-updates for security patches. Patched binaries may differ from the original set submitted for certification, according to Canonical's FIPS documentation. Before changing channels, check the workload's certification requirements and follow Canonical's FIPS procedures. Do not switch to a generic kernel simply to get a higher version number.

Symptoms can be checked, but cannot confirm compromise

These notices provide no IOCs for detecting intrusion, such as malware hashes or callback destinations. The KASAN example in the patch comes from testing the bug, rather than a report of exploitation in the wild. Kernel logs can be used to look for OCFS2 and memory errors, but a typical machine may not have KASAN enabled.

sudo dmesg | grep -Ei 'ocfs2|fast.symlink|use-after-free|out-of-bounds'

If symptoms appear, preserve the logs and record the volume's origin for analysis. An absence of messages does not establish that the system is safe, and errors can also result from corrupt data. Avoid mounting images of unknown origin on production systems. The notices provide no specific workaround to use in place of the patches.

How I would schedule the fixes

I would start by checking which machines use OCFS2 or the FIPS versions listed in the notices, then schedule updates and reboots for that group first. I would put the other flavors in the notices into maintenance windows too, with patch entitlements and external modules ready, without waiting for symptoms, and record the check date along with the status from both the USNs and CVE pages.

Sources: Ubuntu USN-9164-1, USN-9163-1, USN-9162-1, USN-9161-1, USN-9160-1, CVE-2026-74350, Canonical FIPS management and FIPS and security patches, plus the primary sources linked in the article. Information current as of 19 Nov. 2026. I will come back and update this later.

Want us to set this up?

Get help with server setup, configuration, migration, or troubleshooting. Save time for the work that matters.

Get a quote

Hit something like this? Stuck somewhere?

Come trade notes on the LinuxThai board

→ Continue on the board

Comments 0

No comments yet — be the first