pull-request: Fixes: b2b56a163230 ("gpio: tegra186: Check GPIO pin permission before access.")
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-nvidia (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Noble |
Fix Released
|
Undecided
|
Unassigned | ||
linux-nvidia-6.5 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The controller has several register bits describing access control
information for a given GPIO pin. When SCR_SEC_[R|W]EN is unset, it
means we have full read/write access to all the registers for given GPIO
pin. When SCR_SEC[R|W]EN is set, it means we need to further check the
accompanying SCR_SEC_G1[R|W] bit to determine read/write access to all
the registers for given GPIO pin.
This check was previously declaring that a GPIO pin was accessible
only if either of the following conditions were met:
- SCR_SEC_REN + SCR_SEC_WEN both set
or
- SCR_SEC_REN + SCR_SEC_WEN both set and
SCR_SEC_G1R + SCR_SEC_G1W both set
Update the check to properly handle cases where only one of
SCR_SEC_REN or SCR_SEC_WEN is set.
CVE References
no longer affects: | linux-nvidia-6.5 (Ubuntu Noble) |
This bug is awaiting verification that the linux-nvidia- 6.5/6.5. 0-1021. 22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification- needed- jammy-linux- nvidia- 6.5' to 'verification- done-jammy- linux-nvidia- 6.5'. If the problem still exists, change the tag 'verification- needed- jammy-linux- nvidia- 6.5' to 'verification- failed- jammy-linux- nvidia- 6.5'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!