[AutoPR- Security] Patch libinput for CVE-2026-50292 [HIGH]

[azurelinux-security]

Auto Patch libinput for CVE-2026-50292.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1133276&view=results

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

What does the PR accomplish, why was it needed?

• Auto Patch libinput for CVE-2026-50292 (HIGH).

Change Log

• CVE-2026-50292

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-50292

Test Methodology

• Pipeline build id: Buddy Build URL

[kgodara912]

Buddy build

[kgodara912]

AI Patch Review:
The backport correctly adapts upstream commit b2bde9504d42a5976d76e1f27c640dc561fbd99b for libinput 1.25.0:

• Adds a local sanitize_phys() function that replaces control characters (< 0x20 and 0x7f) with '?', preventing \n injection into udev properties via malicious UI_SET_PHYS
• Uses manual memory management (char * + explicit free()) appropriate for 1.25.0's coding style, rather than the newer autofree/steal() macros from later releases
• Properly handles ownership transfer (*phys_attr = phys; phys = NULL;) and cleanup on all paths