Audio: SRC: Add safeguard against missing, wrong size or type init data #8004
Conversation
|
@lgirdwood what Intel platforms are still using IPC3? What Intel platform completely switched to Zephyr? Do you support IPC3 + Zephyr? We plan to deprecate XTOS starting with Q4 on i.MX platforms. But we will still be using IPC3 + Zephyr for a while ( I guess) |
jsarha
force-pushed
the
oss-fuzz-59318-v2
branch
from
70b777b to
621279c
Compare
None on main. Only older platforms using stable-v2.2 branch for fixes only.
All Intel platforms on main. i.e. everything from Tigerlake onwards. All older platforms are on stable v2.2 branch with xtos + IPC3. |
In some error situations the configuration init_data may be NULL, and in such a situations we should fail gracefully and not crash. Also adds check that the IPC message is of correct type and for IPC3 only that it is of correct type. Signed-off-by: Jyri Sarha <jyri.sarha@linux.intel.com>
jsarha
force-pushed
the
oss-fuzz-59318-v2
branch
from
621279c to
c78efeb
Compare
|
SOFCI TEST |
|
Looks ready to go, just needs a clean CI run to merge. |
9 participants
In some error situations the configuration init_data may be NULL, and in such a situations we should fail gracefully and not crash. Also adds check that the IPC message is of correct type and for IPC3 only that it is of correct type.
This is a reincarnation of #7830 that was reverted due to CI problems: #7985
The message type check is now done for IPC3 only.