ZDF
Sign inSign up

Vulnerabilities

Vulnerability · AZL-110441

CVE-2026-92482 affecting package kernel 6.6.157.1-1

Published Sep 17, 2026 · catalog updated Oct 23, 2026 · affecting package kernel 6.6.157.1-1

Last checked Oct 24, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for AZL-110441. A missing EPSS score is not a low risk. Compare affecting package kernel 6.6.157.1-1 with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (affecting package kernel 6.6.157.1-1).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Unknown—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Not established
Affected products
Azure Linux:3 kernel

In the Linux kernel, the following vulnerability has been resolved: pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip The gpio_chip is allocated with device-managed memory but registered with the non-managed gpiochip_add_data(). This was harmless while the drivers were built-in, but once they can be built as modules and unbound/rmmod'd, devm frees the gpio_chip's memory while it is still registered, causing a use-after-free. Register it with devm_gpiochip_add_data() so it shares the same device-managed lifecycle, which also lets the manual gpiochip_remove() error paths go away.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Azure Linux:3 kernel0 → 6.6.157.1-1

How to fix AZL-110441

  • Upgrade

    AZL-110441 lists a fix boundary at 6.6.157.1-1. Compare the installed build with that boundary before you change production.

  • Version check

    Fixed in 6.6.157.1-1

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for AZL-110441. A missing EPSS score is not a low risk. Compare affecting package kernel 6.6.157.1-1 with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 0 → 6.6.157.1-1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Sep 17, 2026 · OpenSSF OSV / OSV Scanner

    Detected

    In the Linux kernel, the following vulnerability has been resolved: pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip The gpio_chip is allocated with device-managed memory but registered with the non-managed gpiochip_add_data(). This was harmless while the drivers were built-in, but once they can be built as modules and unbound/rmmod'd, devm frees the gpio_chip's memory while it is sti

  2. Oct 23, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    kernel fixed in 6.6.157.1-1

  3. Oct 23, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    In the Linux kernel, the following vulnerability has been resolved: pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip The gpio_chip is allocated with device-managed memory but registered with the non-managed gpiochip_add_data(). This was harmless while the drivers were built-in, but once they can be built as modules and unbound/rmmod'd, devm frees the gpio_chip's memory while it is sti

Sources

References

Freshness

Last verified in this catalog Oct 23, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • OpenSSF OSV / OSV ScannerOct 24, 2026