Ubuntu
cryptsetup package

Gutsy: cryptsetup leaves /dev/mapper/temporary-cryptsetup-[0-9]+ devices lying around

Bug #162582 reported by Swâmi Petaramesh
254
Affects Status Importance Assigned to Milestone
cryptsetup (Debian)
Fix Released
Unknown
cryptsetup (Ubuntu)
Fix Released
Undecided
Reinhard Tartler

Bug Description

Binary package hint: cryptsetup

In some situations (I could not yet clearly determine in which exact conditions this happens), after running cryptsetup, a device /dev/mapper/temporary-cryptsetup-[0-9]+ (pidnum ?) is left lying around.

Looks like the same as reported in Debian bug #444914

Not sure what this device actually corresponds to or if it might allow unauthorized access to encrypted content, so I check this as a potential security vulnerability.

Bug Watch Updater (bug-watch-updater)
Changed in cryptsetup:
status: Unknown → Fix Committed
Revision history for this message
Peter Wainwright (prw) wrote :

This looks to be the same bug I have been trying to analyze in Ubuntu bug #148003. It was reported there that the existence of this stale device node often prevents auto-mounting of encrypted USB memory sticks, etc.

There appears to be a race condition in the processes spawned by udev. The file /dev/mapper/temporary-cryptsetup-XXXX is created and then almost immediately destroyed. But it appears that the "remove" event gets processed before the "add" event is finished, with unfortunate results.

Bug Watch Updater (bug-watch-updater)
Changed in cryptsetup:
status: Fix Committed → Fix Released
Revision history for this message
Reinhard Tartler (siretart) wrote :

This looks like another manifestation of bug #132373. At least debian claims that.

Could you please check if this still happens with cryptsetup 2:1.0.5-2ubuntu2.1 or later? if not, this bug can be marked as dupe of bug #132373.

Changed in cryptsetup:
status: New → Incomplete
Revision history for this message
Swâmi Petaramesh (swami-petaramesh) wrote :

I haven't seen it happen again since I installed cryptsetup 2:1.0.5-2ubuntu2.1, but as it was previously happening rather sporadically and inconsistently, it will take me more time before I can be positive about it.

Revision history for this message
Reinhard Tartler (siretart) wrote :

I have now merged the debian package from debian that claims to have this bug merged, so I'm closing this bug.

If you see it in intrepid again, please reopen it again. Thanks.

Changed in cryptsetup:
assignee: nobody → siretart
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.