Skip to content

v2025.05: sof-ctl introduces Security problem NULL DT_RUNPATH #10070

Description

@pacho2

Hello,

While trying to package the last version of SOF firmware for Gentoo:
https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-firmware/sof-firmware

I noticed that, starting from this new 2025.05 version, we get this warning:

scanelf: rpath_security_checks(): Security problem NULL DT_RUNPATH in /var/tmp/portage/sys-firmware/sof-firmware-2025.05/image/usr/bin/sof-ctl

Something changed in the generated binary as compared to the previous binary provided in 2025.01.1 has no warning at all.

Thanks a lot for your help.

Activity

  1. lgirdwood commented on Jun 25, 2025

    @lgirdwood
    Member

    The SDK has been updated to build with a local ALSA git repo instead of ALSA release, looks like this can be fixed with a make deploy rule that builds sof-ctl with the system ALSA library OR we dont build sof-ctl with local ALSA.

  2. added
    bugSomething isn't working as expected
    on Jun 25, 2025
  3. lgirdwood commented on Jun 27, 2025

    @lgirdwood
    Member

    This should fix the issue, lets see it passes CI with current CI infra. #10073

  4. added theissue type on Jun 27, 2025
  5. ujfalusi commented on Jul 4, 2025

    @ujfalusi
    Contributor

    @pacho2, also to note that the tools USE flag can be optional, these binaries are not needed for users, they are useful for developers or for debugging.

  6. pacho2 commented on Jul 5, 2025

    @pacho2
    Author

    @pacho2, also to note that the tools USE flag can be optional, these binaries are not needed for users, they are useful for developers or for debugging.

    Yes, I am the downstream maintainer ;) ... but, following our QA policies, I would need to ignore those warnings forever. Sometimes we need to do that... but it is better if it can be fixed in another way :)

  7. github-actions commented on Sep 4, 2025

    @github-actions

    This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

  8. added
    staleIssue/PR marked as stale and will be closed after 14 days if there is no activity.
    on Sep 4, 2025
  9. pacho2 commented on Sep 11, 2025

    @pacho2
    Author

    It is still valid with the latest version. Thanks

  10. removed
    staleIssue/PR marked as stale and will be closed after 14 days if there is no activity.
    on Sep 12, 2025
  11. added this to the v2.15 milestone on Sep 15, 2025
  12. github-actions commented on Nov 15, 2025

    @github-actions

    This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

  13. added
    staleIssue/PR marked as stale and will be closed after 14 days if there is no activity.
    on Nov 15, 2025
  14. 1 remaining item

  15. removed
    staleIssue/PR marked as stale and will be closed after 14 days if there is no activity.
    on Nov 23, 2025
  16. github-actions commented on Jan 22, 2026

    @github-actions

    This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

  17. added
    staleIssue/PR marked as stale and will be closed after 14 days if there is no activity.
    on Jan 22, 2026
  18. pacho2 commented on Jan 25, 2026

    @pacho2
    Author

    Still valid with 2025.12.1

  19. removed
    staleIssue/PR marked as stale and will be closed after 14 days if there is no activity.
    on Jan 26, 2026
  20. github-actions commented on Mar 27, 2026

    @github-actions

    This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

  21. added
    staleIssue/PR marked as stale and will be closed after 14 days if there is no activity.
    on Mar 27, 2026
  22. pacho2 commented on Apr 5, 2026

    @pacho2
    Author

    Still valid

  23. removed
    staleIssue/PR marked as stale and will be closed after 14 days if there is no activity.
    on Apr 6, 2026
  24. github-actions commented on Jun 5, 2026

    @github-actions

    This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

  25. added
    staleIssue/PR marked as stale and will be closed after 14 days if there is no activity.
    on Jun 5, 2026
  26. pacho2 commented on Jun 6, 2026

    @pacho2
    Author

    still valid

  27. removed
    staleIssue/PR marked as stale and will be closed after 14 days if there is no activity.
    on Jun 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working as expected

    Type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions