Patch ntfs-3g for CVE-2026-42616, CVE-2026-42617, CVE-2026-42618, CVE-2026-46569, CVE-2026-46570, CVE-2026-46571

[jykanase]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

Patch ntfs-3g for CVE-2026-42616, CVE-2026-42617, CVE-2026-42618, CVE-2026-46569, CVE-2026-46570, CVE-2026-46571

Change Log

• ntfs-3g.spec
• CVE-2026-42616.patch
• CVE-2026-42617.patch
• CVE-2026-42618.patch
• CVE-2026-46569.patch
• CVE-2026-46570.patch
• CVE-2026-46571.patch

Does this affect the toolchain?

No

Associated issues

• #xxxx

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-42616
• https://nvd.nist.gov/vuln/detail/CVE-2026-42617
• https://nvd.nist.gov/vuln/detail/CVE-2026-42618
• https://nvd.nist.gov/vuln/detail/CVE-2026-46569
• https://nvd.nist.gov/vuln/detail/CVE-2026-46570
• https://nvd.nist.gov/vuln/detail/CVE-2026-46571

Test Methodology

• Local Build

• Patch application during build

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[jykanase]

Patch Analysis:

1. Upstream reference:
   CVE-2026-42616: https://github.com/user-attachments/files/29754085/ntfs-3g_2022.10.3-cve_2026-04_2.patch
   CVE-2026-42617: https://github.com/user-attachments/files/29754124/ntfs-3g_2022.10.3-cve_2026-04_3.patch
   CVE-2026-42618: https://github.com/user-attachments/files/29754051/ntfs-3g_2022.10.3-cve_2026-04_1.patch
   CVE-2026-46569: https://github.com/user-attachments/files/29754809/ntfs-3g_2022.10.3-cve_2026-04_4.patch
   CVE-2026-46570: https://github.com/user-attachments/files/29755270/ntfs-3g_2022.10.3-cve_2026-04_6.patch
   CVE-2026-46571: https://github.com/user-attachments/files/29755148/ntfs-3g_2022.10.3-cve_2026-04_5.patch
2. The patches match the upstream patch exactly.
3. The patches were applied during the build (check rpm.log).
4. Each patch includes an upstream reference.