"value":"In the Linux kernel, the following vulnerability has been resolved:\n\npower: supply: core: Fix boundary conditions in interpolation\n\nThe functions power_supply_temp2resist_simple and power_supply_ocv2cap_simple\nhandle boundary conditions incorrectly.\nThe change was introduced in a4585ba2050f460f749bbaf2b67bd56c41e30283\n(\"power: supply: core: Use library interpolation\").\nThere are two issues: First, the lines \"high = i - 1\" and \"high = i\" in ocv2cap\nhave the wrong order compared to temp2resist. As a consequence, ocv2cap\nsets high=-1 if ocv>table[0].ocv, which causes an out-of-bounds read.\nSecond, the logic of temp2resist is also not correct.\nConsider the case table[] = {{20, 100}, {10, 80}, {0, 60}}.\nFor temp=5, we expect a resistance of 70% by interpolation.\nHowever, temp2resist sets high=low=2 and returns 60."
"value":"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: power: supply: core: Fix boundary conditions in interpolation The functions power_supply_temp2resist_simple and power_supply_ocv2cap_simple handle boundary conditions incorrectly. El cambio se introdujo en a4585ba2050f460f749bbaf2b67bd56c41e30283 (\"power: supply: core: Use library interpolation\"). Hay dos problemas: primero, las l\u00edneas \"high = i - 1\" y \"high = i\" en ocv2cap tienen el orden incorrecto en comparaci\u00f3n con temp2resist. Como consecuencia, ocv2cap establece high=-1 si ocv>table[0].ocv, lo que provoca una lectura fuera de los l\u00edmites. Segundo, la l\u00f3gica de temp2resist tampoco es correcta. Considere el caso table[] = {{20, 100}, {10, 80}, {0, 60}}. Para temp=5, esperamos una resistencia del 70 % por interpolaci\u00f3n. Sin embargo, temp2resist establece high=low=2 y devuelve 60."
