Nixpkgs security tracker

Try the new UI
Login with GitHub
⚠️ You are using a production deployment that is still only suitable for demo purposes. Any work done in this might be wiped later without notice.

Suggestion detail

Dismissed
(max. allowed matches exceeded)
created 1 week, 6 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
ocfs2: fix buffer head management in ocfs2_read_blocks()

In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix buffer head management in ocfs2_read_blocks() In ocfs2_read_blocks(), caller should't assume that buffer head returned by 'sb_getblk()' is exclusively owned and so 'put_bh()' always drops b_count from 1 to 0. If it is not so, buffer head remains on hold and likely to be returned by the next call to 'sb_getblk()' unchanged - that is, with BH_Uptodate bit set even if it has failed validation previously, thus allowing to insert that buffer head into OCFS2 metadata cache and submit it to upper layers. To avoid such a scenario, BH_Uptodate should be cleared immediately after 'validate()' callback has detected some data inconsistency.

Affected products

Linux
  • ==65cbd1279f4b999d56a838344a30642db24cd215
  • =<7.1.*
  • ==01f93d5e36753fc4d06ec67f05ce78c9c6f2dd56
  • <6371a07148ee979af22a9d6f4c277462953a9a4a
  • <5927acb3e2c99985a14adecd9d1b67ba191c622d
  • ==6c150df9c2e80b5cf86f5a0d98beb7390ad63bfc
  • ==4.20
  • <4ab17e328522a4df5fe0f0dcf39098118b1feeaa
  • =<6.18.*
  • =<6.12.*
  • =<5.10.*
  • <4.15
  • =<5.15.*
  • <9e7a057934cdd58e4cc94350bcfe5367bbee0f8e
  • <4.20
  • =<6.6.*
  • ==97e1db17bc1ef4c2e1789bc9323c7be44fba53f8
  • <0e389fc290c350c67591abf4c367119f4689f310
  • <4.20
  • =<*
  • =<6.1.*
  • <ecb3f9386f4353034caef77239473c627232db17
  • <a4eae1499c760949a93459d11390bd1fd823d31d
  • <4.10
  • <4.5
  • <61f7a5acb3bf8fc97dad78f54b1e8d0e1c819766