CVE-2026-14447 · Infrastructure
NO FIX YET
An off-by-one bounds check in the memss-mfw.c driver's ext_mem_obj_get_page function can return a physical address outside the intended range. A local attacker with System-level execution privileges can read that information.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
No product ranges from the sources yet.
Who cares android, kernel-driver
Unknown from the sources.
No fix yet, per the sources.
In ext_mem_obj_get_page of memss-mfw.c, there is a possible way to return an out of bounds physical address via an off-by-one check due to an incorrect bounds check. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.